From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Antonino Daplas <adaplas@pol.net>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Petr <vandrove@vc.cvut.cz>
Subject: Re: [Linux-fbdev-devel] [PATCH]: EDID parser
Date: 03 Apr 2003 00:20:54 +0200 [thread overview]
Message-ID: <1049322054.578.3.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0304022245520.2488-100000@phoenix.infradead.org>
> Let really good. I applied it to my local tree but haven't passed it to BK
> fbdev yet. The only thing I like to see changed is get_EDID. At present it
> accepts a struct pci_dev. Now for generic support for the intel platform
> we can get this from the BIOS. You already have a patch that does this.
> It doesn't need a struct pci_dev in this case. It is possible to get this
> info from the i2c bus but I never seen any drivers do this. What data would
> we have to pass in get the EDID inforamtion? So the question is how
> generic will get_EDID end up being or will we have to have driver specfic
> hooks since I don't pitcure i2c approaches being the same for each video
> card. Petr didn't you attempt this with the matrox driver at one time?
get_EDID() has to be a driver specific hook
EDID via BIOS is a way to get it, BIOS emulation in userland is another,
on PPC, I can retreive it from the firmware device-tree in a different
way with some cards, and finally, I plan to implement i2c sooner or
later with some drivers...
Ben.
next prev parent reply other threads:[~2003-04-02 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1049298087.1993.54.camel@localhost.localdomain>
2003-04-02 21:55 ` James Simmons
2003-04-02 22:20 ` Benjamin Herrenschmidt [this message]
2003-04-03 0:45 ` Antonino Daplas
2003-04-03 6:44 ` Benjamin Herrenschmidt
2003-04-03 7:05 ` Benjamin Herrenschmidt
2003-04-03 2:07 Petr Vandrovec
2003-04-03 7:40 ` Sven Luther
2003-04-03 11:05 Petr Vandrovec
2003-04-03 12:20 ` Benjamin Herrenschmidt
2003-04-03 12:38 ` Sven Luther
2003-04-03 13:55 Petr Vandrovec
2003-04-03 14:15 ` Sven Luther
2003-04-03 15:21 ` Alan Cox
2003-04-03 16:21 ` Sven Luther
2003-04-03 16:18 ` Alan Cox
2003-04-03 16:33 ` Geert Uytterhoeven
2003-04-03 17:10 ` Sven Luther
2003-04-03 16:15 ` Alan Cox
2003-04-03 17:18 ` Sven Luther
2003-04-03 16:29 ` Alan Cox
2003-04-03 14:05 Petr Vandrovec
2003-04-03 13:11 ` Sven Luther
2003-04-03 14:38 Petr Vandrovec
2003-04-03 13:48 ` Sven Luther
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=1049322054.578.3.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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®