From: Eric Anholt <eric@anholt.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: Kyle McMartin <kyle@infradead.org>,
airlied@redhat.com, linux-kernel@vger.kernel.org,
dri-devel@lists.sourceforge.net, jbarnes@virtuousgeek.org,
marko.ristola@kolumbus.fi
Subject: Re: [PATCH] drm: edid revision 0 is valid
Date: Tue, 10 Mar 2009 20:10:26 -0700 [thread overview]
Message-ID: <1236741026.9354.3.camel@gaiman> (raw)
In-Reply-To: <20090311025636.GA31718@shareable.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Wed, 2009-03-11 at 02:56 +0000, Jamie Lokier wrote:
> Kyle McMartin wrote:
> > - if (edid->revision <= 0 || edid->revision > 3) {
> > + if (edid->revision > 3) {
> > DRM_ERROR("EDID has minor version %d, which is not between 0-3\n", edid->revision);
> > goto bad;
>
> Ahem. EDID version 1.4 exists too, in fact it's the current version.
> EDID 1.5+ doesn't exist, but it should be backward compatible when it does.
>
> I'm doing a lot of work on another EDID parser, including full DMT and
> CEA-861 mode tables, monitor hotplug, all quirks from Xorg and the
> kernel, EDID 1.4 support w/ CVT calculation, etc. right now for an
> embedded Linux video project. Would there be any interest
> incorporating parts of that work?
There's work going on for CEA-861 and syncing KMS against UMS. But
certainly we love fixes when we don't even have to write them ourselves.
--
Eric Anholt
eric@anholt.net eric.anholt@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-11 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:31 [PATCH] drm: edid revision 0 is valid Kyle McMartin
2009-02-25 1:44 ` Jesse Barnes
2009-03-11 2:56 ` Jamie Lokier
2009-03-11 3:10 ` Eric Anholt [this message]
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=1236741026.9354.3.camel@gaiman \
--to=eric@anholt.net \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jamie@shareable.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kyle@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marko.ristola@kolumbus.fi \
/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.