From: Eric Anholt <eric@anholt.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: worth submitting a detailed EDID structure?
Date: Fri, 02 Jan 2009 14:55:56 -0800 [thread overview]
Message-ID: <1230936956.6095.5.camel@gaiman.anholt.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0901020906310.12465@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On Fri, 2009-01-02 at 09:08 -0500, Robert P. J. Day wrote:
> just noticed the header file include/video/edid.h, which defines
> video EDID info as simply:
>
> struct edid_info {
> unsigned char dummy[128];
> };
>
> a couple months back, i had to mess with EDID info and defined a
> detailed structure to manipulate EDID fields. is it worth submitting
> that as a patch and union'ing that with the above? not a big deal for
> me either way.
The KMS code already has detailed EDID structures in drm_edid.h, for
what it's worth. We still need to get CEA extension bits ported over,
though.
--
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 --]
next prev parent reply other threads:[~2009-01-02 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 14:08 Robert P. J. Day
2009-01-02 22:55 ` Eric Anholt [this message]
2009-01-03 9:21 ` Robert P. J. Day
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=1230936956.6095.5.camel@gaiman.anholt.net \
--to=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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
all inboxes | Powered by JetHome®