From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Discuss issues related to the xorg tree <xorg@lists.freedesktop.org>
Subject: Re: [Linux-fbdev-devel] VESA, EDID & flat panels
Date: Tue, 04 Oct 2005 13:43:55 +1000 [thread overview]
Message-ID: <1128397436.31063.0.camel@gaston> (raw)
In-Reply-To: <8a0c36780510031618m48c55f45u648d867bcf0130d2@mail.gmail.com>
On Mon, 2005-10-03 at 18:18 -0500, Richard Smith wrote:
> > Somebody around here has access to the VESA specs ? I'm trying to figure
> > out if the EDID block, at least on recent flat panels, tells us wether
> > the panel digital input is 6:6:6 or 8:8:8 ... If it's 6:6:6, we should
> > enable dithering in drivers like radeon and "nv", while if 8:8:8, we
> > should not. If not enabling it on a 6 bits panel, we end up with crappy
> > looking gradients, if enabling it on a 8 bits panel, we basically end up
> > sending a 6 bits signal to a 8 bits panel, thus reducing the quality.
>
> We have a copy from a few years ago. Its not too descriptive if
> IIRC. I'll try to look at it tomorrow.
I found a lot of stuff on VESA Public site in fact. Looks like we really
need to write some infrastructure to get to the EDID extensions :) They
contain all sort of useful infos, though unfortunately, all of the
panels I've come accross so far didn't seem to implement them =P
Ben.
next prev parent reply other threads:[~2005-10-04 3:43 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 ` Benjamin Herrenschmidt [this message]
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
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=1128397436.31063.0.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox