From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: dri-devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [Dri-devel] Rage128 and Radeon patches
Date: 15 Aug 2003 00:04:19 +0200 [thread overview]
Message-ID: <1060898658.13316.4.camel@gaston> (raw)
In-Reply-To: <20030814160038.11209.qmail@web14906.mail.yahoo.com>
On Thu, 2003-08-14 at 18:00, Jon Smirl wrote:
> --- Benjamin Herrenschmidt <benh@kernel.crashing.org>
> wrote:
> > This is a problem. We also parse it to find the DFP
> > EDID and/or flat panel informations, do that work
> > with the real ROM ? I don't know much about x86
> > BIOSes, but at least for the DFP EDID, I suppose
> > that one is read in RAM by the BIOS, not in the
> > ROM...
>
> On x86 machines low RAM contains a copy of the ROM,
> now you are getting a pointer to the real ROM. The
> contents are identical. The only difference is that
> you need to use the readb()/readw()/etc macros to read
> it. On the x86 readb() does nothing, but on other
> platforms it will trigger a PCI read cycle. This plus
> side to this is that you can use multiple video cards.
Well... Again, this has to be verified in real life, but
my understanding is that the BIOS code, once it has probed
the DFP flat panel, will put the EDID data in RAM somewhere
within the copy of the BIOS, which is where we then find
it... The best thing would still be, of course, to implement
full DDC probing in radeonfb like XFree does. This has been
on my todolist for a while now, but I lack time.
Ben.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-14 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 3:43 Rage128 and Radeon patches Jon Smirl
2003-08-14 10:42 ` [Dri-devel] " Benjamin Herrenschmidt
2003-08-14 16:00 ` Jon Smirl
2003-08-14 22:04 ` Benjamin Herrenschmidt [this message]
2003-08-14 22:47 ` Jon Smirl
2003-08-15 8:18 ` Benjamin Herrenschmidt
2003-08-14 13:22 ` Alex Deucher
2003-08-14 17:13 ` [Linux-fbdev-devel] " Jon Smirl
2003-08-14 18:06 ` Alex Deucher
2003-08-14 18:32 ` Steven Newbury
2003-08-14 18:26 ` dri fb drivers [was: Re: Rage128 and Radeon patches] Otto Solares
2003-08-14 18:55 ` dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
2003-08-14 19:33 ` dri fb drivers [was: " James Simmons
2003-08-14 20:18 ` Otto Solares
2003-08-14 21:45 ` Re: dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
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=1060898658.13316.4.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--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;
as well as URLs for NNTP newsgroup(s).