Linux Media Controller development
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Monica, Agnes" <Agnes.Monica@analog.com>,
	"v4l2-library@linuxtv.org" <v4l2-library@linuxtv.org>,
	linux-media <linux-media@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [V4l2-library] FourCC support
Date: Tue, 22 Jul 2014 09:23:25 +0200	[thread overview]
Message-ID: <53CE116D.8010404@xs4all.nl> (raw)
In-Reply-To: <E2B3634EC825DA45A0EB7D5409D69FBE584D03FA@NWD2MBX6.ad.analog.com>

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.

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


       reply	other threads:[~2014-07-22  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E2B3634EC825DA45A0EB7D5409D69FBE584D03FA@NWD2MBX6.ad.analog.com>
2014-07-22  7:23 ` Hans Verkuil [this message]
2014-07-22  7:37   ` [V4l2-library] FourCC support Hans Verkuil
2014-07-23  5:04     ` Monica, Agnes
2014-07-23  6:39       ` Hans Verkuil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CE116D.8010404@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=Agnes.Monica@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-media@vger.kernel.org \
    --cc=v4l2-library@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox