linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@alcove.fr>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.5-ac12] New Sony Vaio Motion Eye camera driver
Date: Wed, 13 Jun 2001 12:24:14 +0200	[thread overview]
Message-ID: <E15A7os-0003e9-00@come.alcove-fr> (raw)
In-Reply-To: <Pine.LNX.4.31.0106121549130.4477-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.31.0106121549130.4477-100000@penguin.transmeta.com>

> I got just the YUV code from Gatos, and a few months ago it took less than
> an hour to merge just that part (and most of that was compiling and
> testing).

Me too. After some days playing with it it seems that the Rage Mobility
Card (from the Vaio Picturebook C1VE <- that's where we started the
discussion):
	- has almost no acceleration in XFree, including the 4.1.0 release
	- has Xv YUV->RGB acceleration in Gatos (but that's all, no direct
	  video input etc).

> The rest of Gatos is obviously more experimental, but the YUV code looks
> quite sane.

Well, not quite... I've had several X lockups while using the YUV 
acceleration code. Let's say one lockup per half an hour.

Even the performances are controversial: with 320x240, I achieve 
great performance with xawtv/meye driver, I can even use the hardware
scaling facilities (well, the xawtv sources need a little hacking for
that), but in 640x480 the framerate achieved with Xv is below the
one I get by converting YUV->RGB in software...

But the main question remains: does the MotionEye camera support
overlay or not ? It could be that it is connected to the feature
connector of the ATI board for doing direct video input/output
(but no X driver recognizes this connector today). The motion jpeg
chip this camera is based on definately has a video output.

Or it could just be the application who gets YUV data from the chip
then send it directly to the video board. Today this works, almost
(because we need a patched X - read gatos - and a patched xawtv - in
order to do scaling).

Stelian.
-- 
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|

  parent reply	other threads:[~2001-06-13 10:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 20:58 [PATCH 2.4.5-ac12] New Sony Vaio Motion Eye camera driver 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-06-10 13:25 Stelian Pop
2001-06-10 14:39 ` Alan Cox
2001-06-10 15:57   ` Stelian Pop
2001-06-10 15:58     ` Alan Cox
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

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=E15A7os-0003e9-00@come.alcove-fr \
    --to=stelian@alcove.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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).