All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
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 12:27:52 -0700	[thread overview]
Message-ID: <20110415122752.59d90130@jbarnes-desktop> (raw)
In-Reply-To: <20110415121931.42a24970@jbarnes-desktop>

On Fri, 15 Apr 2011 12:19:31 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Fri, 15 Apr 2011 15:13:02 -0400
> Adam Jackson <ajax@redhat.com> wrote:
> > 	info->color_formats = DRM_COLOR_FORMAT_RGB444;
> > 	if (edid->features & DRM_EDID_FEATURE_YCRCB444)
> > 		info->color_formats |= DRM_COLOR_FORMAT_YCBCR444;
> > 	if (edid->features & DRM_EDID_FEATURE_YCRCB422)
> > 		info->color_formats |= DRM_COLOR_FORMAT_YCBCR422;
> > 
> > ... which is corrected to not include RGB uselessly in the 
> > DRM_EDID_FEATURE_* tokens.  I should have noticed that in your first 
> > patch, whoops.
> 
> I don't think EDID supports that?  The docs I have here imply that
> either RGB, RGB + YCrCb444 or RGB + YCrCb444 + YCrCb422 are the only
> things we can report.
> 
> Or is there a CEA block extension that allows for more granularity?

Nevermind, I even had the define correct, I just missed it when adding
the conditionals.  Will fix things to look like the above as it's nicer
than doing the switch.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-04-15 19:28 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 [this message]
2011-04-15 19:36     ` Adam Jackson
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=20110415122752.59d90130@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=dri-devel@lists.freedesktop.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.