All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: parse color format support for digital displays
Date: Fri, 15 Apr 2011 15:36:22 -0400	[thread overview]
Message-ID: <4DA89E36.2040803@redhat.com> (raw)
In-Reply-To: <20110415121931.42a24970@jbarnes-desktop>

On 4/15/11 3:19 PM, Jesse Barnes wrote:

> Or is there a CEA block extension that allows for more granularity?

CEA has bits for the two YCbCr formats too, which we should also parse 
since there's plenty of 1.3+CEA blocks in the world thanks to HDMI.  For 
CEA blocks version 2 and up (version number in byte 2 of the CEA block, 
zero-based indexing), (1 << 5) of byte 3 is 4:4:4 and (1 << 4) is 4:2:2. 
  Same byte as what we already check for EDID_BASIC_AUDIO, if that's any 
clearer.  CEA spec contains the same language about always supporting 
RGB though.

I don't have a good answer for what to do if you have a 1.4+CEA block 
and the two bitfields are inconsistent, besides violence against the 
monitor vendor.

- ajax

  parent reply	other threads:[~2011-04-15 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 18:40 [PATCH] drm: parse color format support for digital displays Jesse Barnes
2011-04-15 19:13 ` Adam Jackson
2011-04-15 19:19   ` Jesse Barnes
2011-04-15 19:27     ` Jesse Barnes
2011-04-15 19:36     ` Adam Jackson [this message]
2011-04-15 19:44       ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2011-04-15 20:48 Jesse Barnes

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=4DA89E36.2040803@redhat.com \
    --to=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.