linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: stelian.pop@fr.alcove.com
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.5-ac12] New Sony Vaio Motion Eye camera driver
Date: Sun, 10 Jun 2001 16:58:42 +0100 (BST)	[thread overview]
Message-ID: <E1597bu-0006lf-00@the-village.bc.nu> (raw)
In-Reply-To: <20010610175730.B15945@ontario.alcove-fr> from "Stelian Pop" at Jun 10, 2001 05:57:30 PM

> Yes. But, even if I know how to program the mchip to output to
> the video bus, there is something missing to enable overlay
> (either in the mchip or in the ati video driver).

It could be using the YUV digital inputs to the ATI chip. It seems however
also quite likely to me that windows is doing the following

1.	Issuing USB transfers which put the data into video ram overlay buffers
	(ie the DMA from the USB controller)

2.	Using the YUV overlay/expand hardware in the ATI card 
	(see www.gatos.org for X stuff for ATI for this)

> 


  reply	other threads:[~2001-06-10 16:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 13:25 [PATCH 2.4.5-ac12] New Sony Vaio Motion Eye camera driver Stelian Pop
2001-06-10 14:39 ` Alan Cox
2001-06-10 15:57   ` Stelian Pop
2001-06-10 15:58     ` Alan Cox [this message]
2001-06-10 16:46       ` Stelian Pop
2001-06-10 19:07         ` Linus Torvalds
2001-06-10 23:41           ` egger
2001-06-11  0:13             ` Linus Torvalds
2001-06-11 19:37               ` egger
2001-06-12 20:58 Alex Deucher
2001-06-12 22:50 ` egger
2001-06-13 13:05   ` Alex Deucher
2001-06-12 22:51 ` Linus Torvalds
2001-06-13  6:33   ` egger
2001-06-13 10:24   ` Stelian Pop
2001-06-14 21:36     ` Linus Torvalds
2001-06-15 21:10     ` Stelian Pop
2001-06-28 19:11     ` volodya
2001-06-29  9:29       ` Stelian Pop
2001-06-13 13:09   ` Alex Deucher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1597bu-0006lf-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).