From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>,
Magnus Damm <damm@opensource.se>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: aty128fb and EDID
Date: 10 Feb 2003 11:34:20 +0100 [thread overview]
Message-ID: <1044873260.11921.24.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <Pine.GSO.4.21.0302101034180.25020-100000@vervain.sonytel.be>
On Mon, 2003-02-10 at 10:35, Geert Uytterhoeven wrote:
> On Sun, 9 Feb 2003, Kevin B. Hendricks wrote:
> > Steal the code from the radeon dirver in the kernel. It finds and parses
> > the EDID block in OF for ppc linux systems for LCD.
>
> I guess you actually meant:
>
> | Move the code out of the radeon driver and make it sufficiently generic so it
> | can be used by the aty128 and other drivers?
That code is also shared by rivafb. It's rather LCD/DFP specific for
now, I would _much_ prefer some more generic EDID parser. So far,
I haven't been able to find any specification of the edid block,
this is annoying as I'd like to deduce a proper default mode for
CRTs as well, and some informations about backlight ranges (if any
in the EDID).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-10 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 23:26 aty128fb and EDID Magnus Damm
2003-02-10 0:40 ` Kevin B. Hendricks
2003-02-10 9:35 ` Geert Uytterhoeven
2003-02-10 10:14 ` Magnus Damm
2003-02-10 13:16 ` Kevin B. Hendricks
2003-02-10 18:41 ` Dan Burcaw
2003-02-10 18:59 ` Kevin B. Hendricks
2003-02-10 10:34 ` Benjamin Herrenschmidt [this message]
2003-02-10 12:36 ` Kevin B. Hendricks
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=1044873260.11921.24.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=damm@opensource.se \
--cc=geert@linux-m68k.org \
--cc=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).