Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: VESA, EDID & flat panels
Date: Mon, 10 Oct 2005 15:50:46 +1000	[thread overview]
Message-ID: <1128923447.17365.117.camel@gaston> (raw)
In-Reply-To: <8a0c36780510040535g16a3074p66384d8b07d03ea1@mail.gmail.com>

On Tue, 2005-10-04 at 07:35 -0500, Richard Smith wrote:
> > So I wonder how widespread really is that EEDID stuff... I'm afraid the
> > reason a lot of monitors come with a windows install CD is that they do
> > _not_ provide those infos via EDID, but windows has a database with
> > per-monitor infos (as Apple actually has in OS X) and we should probably
> > do something similar. (but not in the kernel)
> 
> Our experience agrees with you that the EEDID stuff is not well used. 
> We make some LCD driver products and I'm pretty sure we didn't include
> the EEDID info.
> 
> I gave the specs a quick look and I don't see anything in (thats
> obvious) there that would allow you to see if the panel is 666 or 888.
> The specs are somewhat less than clear in several cases so I'll be
> happy to review any sections closer if you think one might be a
> possibility.

Look at the EDID EXTENSIONS spec. Extension 0x40 contains the panel
component bit definition iirc. I found so far only one monitor that
implemented that extended block (the Apple 23" Cinema HD display) but
the content seem to be junk =P

Ben.




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

  reply	other threads:[~2005-10-10  5:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 22:53 VESA, EDID & flat panels Benjamin Herrenschmidt
2005-10-03 23:18 ` Richard Smith
2005-10-04  3:43   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-10-04  6:27     ` Antonino A. Daplas
2005-10-04  6:39       ` Benjamin Herrenschmidt
2005-10-04  6:56         ` Antonino A. Daplas
2005-10-04  7:59         ` Antonino A. Daplas
2005-10-04  8:50           ` Benjamin Herrenschmidt
2005-10-04 12:04             ` Antonino A. Daplas
2005-10-04 12:35             ` Richard Smith
2005-10-10  5:50               ` Benjamin Herrenschmidt [this message]
2005-10-04  0:03 ` Antonino A. Daplas
2005-10-10  8:43 ` Egbert Eich

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=1128923447.17365.117.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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