Hi Hardik, On Thursday 22 January 2009 05:57:18 Shah, Hardik wrote: > Hi, > OMAP class of device supports transparency color keying. Color keying > can be source color keying or destination color keying. Can it be both as well? > OMAP3 has three pipelines one graphics plane and two video planes. Any > of these pipelines can go to either the TV or LCD. > > The destination transparency color key value defines the encoded pixels > in the graphics layer to become transparent and display the underlying > video pixels. While the source transparency key value defines the encoded > pixels in the video layer to become transparent and display the > underlying graphics pixels. This color keying works only if the video > and graphics planes are on the same output like TV or LCD and images of > both the pipelines overlapped. > > I propose to have the one ioctl to set the encoded pixel value and type > of color keying source and destination. Also we should have the CID to > enable/disable the color keying functionality. > > Please let us know your opinions/comments. Destination color keying is already available through the S_FBUF and S_FMT ioctls. Selecting source color keying can easily be added to S_FBUF, but setting the actual chromakey is harder. The logical place would be the v4l2_pix_format struct, but that is already full. I guess we should make a new control to set the source chromakey. It's not ideal, but it prevents duplicating existing functionality. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
