Re: [PATCH] OMAP 2/3 V4L2 display driver on video planes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hans Verkuil <hverkuil@xxxxxxxxx> writes:

> On Monday 06 October 2008 08:06:30 Shah, Hardik wrote:
>> 4.  VIDIOC_S/G_OMAP2_COLORKEY:  Color keying allows the pixels with
>> the defined color on the video pipelines to be replaced with the
>> pixels on the graphics pipelines.  I believe similar feature must be
>> available on almost all next generation of video hardware. We can add
>> new ioctl for this feature in V4L2 framework. I think VIDIOC_S_FBUF
>> ioctl is used for setting up the buffer parameters on per buffer
>> basis.  So IMHO this ioctl is not a natural fit for the above
>> functionality. Please provide your comments on same.
>
> Do I understand correctly that if the color in the *video* streams 
> matches the colorkey, then it is replaced by the color in the 
> *framebuffer* (aka menu/overlay)? Usually it is the other way around: 
> if the framebuffer (menu) has chromakey pixels, then those pixels are 
> replaced by pixels from the video stream. That's what the current API 
> does.

The OMAP3 hardware supports both type of keying, but not
simultaneously.

-- 
Måns Rullgård
mans@xxxxxxxxx

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux