Re: [V4l2-library] FourCC support

[Hans Verkuil <hverkuil@xs4all.nl>]

On 07/22/14 09:23, Hans Verkuil wrote:
> Hi Monica,
> 
> The v4l2-library is not the best mailinglist for that so I've added linux-media
> as well, which is more appropriate. I've also added Lars-Peter since he does a
> lot of adv work as well.
> 
> The short answer is that those colorspaces are not supported at the moment,
> but that it is not a problem to add them, provided the driver you are
> working on is going to be upstreamed (i.e., we'd like to have users for
> the API elements we add).
> 
> One note of interest: there is currently no API mechanism to tell userspace
> if the image data is limited or full range. YCbCr is always assumed to be
> limited range and RGB full range. If you need to signal that, then let me
> know. A flags field has been added to struct v4l2_pix_format in the last
> few days that would allow you to add a 'ALT_RANGE' flag, telling userspace
> that the alternate quantization range is used. This flag doesn't exist yet,
> but it is no problem to add it.

To prevent any confusion: the colorspace isn't determined by the format fourcc,
it's a separate colorspace field using the V4L2_COLORSPACE_* defines. The
pixelformat and colorspace are two very different things.

Regards,

	Hans

> 
> Hope this helps,
> 
> 	Hans
> 
> On 07/22/14 08:18, Monica, Agnes wrote:
>> Hi ,
>>
>> One of drivers which we are developing supports formats like sYcc ,
>> AdobeRGB and AdobeYCC601 which was added recently in HDMI spec1.4. So
>> can you please tell me how will these formats be supported by fmt.
>>
>> Regards,
>>
>> Monica
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>