On Wed, Jul 26, 2006 at 09:34:03AM +0200, ext Frantisek Dufka wrote: > could we clarify this a bit? As far as I understand it the omapfb > framebuffer driver (drivers/video/omap/hwa742.c) has access to the Epson > 742 chip and according to kernel source supports YUV->RGB color > conversion when transferring data from main memory to internal video ram > via OMAPFB_UPDATE_WINDOW ioctl defined in > include/asm-arm/arch-omap/omapfb.h. There is color format parameter in > this ioctl and one of the defined ones is OMAPFB_COLOR_YUV420
You can only have one format per plane, and the plane is set up as RGB565 (for obvious reasons). > Do you say that DSP has such driver duplicated in DSP code and accesses > this chip directly? or does the DSP do colorspace conversion in its code > and the features of HWA747 chip and ioctls with OMAPFB_COLOR_YUV420 is > actually not used (maybe because there is some problem with it)? > > I thought DSP only decodes video to shared framebuffer in main memory > and the actual transfer to epson chip is done by omapfb driver i.e. by > ARM CPU from gstreamer or directly from mediaserver code. Correct. > Am I wrong with this? If not, is it possible to add YUV surfaces to > xserver (via Xv or Nokia Xsp extensions) so it could be used from X11 > code in Mplayer or (nonpartched or patched) SDL ? Not at the moment: you need multiple planes, so you can also set up a separate YUV surface, you can't just blit in with a different format. Cheers, Daniel
signature.asc
Description: Digital signature
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
