On Wed, May 17, 2000 at 12:17:12AM +0100, Alan Cox wrote:
> > with this totally device-specific data stream. No client would be able (or
> > want) to understand device-dependent formats. V4L does not seem to have a
> > good place to insert such conversion code into. V4L2 does. In the mean
> > time all drivers produce RGB24 (or GRAY) output - not because they love it
> > but because they must.
>
> No. The API is intended to dump everything in user space. Doing conversions
> in kernel space is bad for applications
Definitely. I am currently converting RGB888 back to YUV and rescale 640x480
down to CIF (or 320x240 up) so the Video compressor codecs build into 'vic'
can use it.
That the ov511 driver is converting it from YUV420 to RGB does not exactly
increase performance.
(I also suspect the conversion in the driver is broken, the colors are way off.)
> > All (or most of) camera drivers are based on CPiA code. It did YUV -> RGB
> > conversion in USB interrupt thread. This is very bad performance-wise. I
> This is broken. They should be outputting YUV not RGB888 to user space.
Yes.
Cao, Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
