From: Jon Smirl <jonsmirl@yahoo.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Thu, 14 Aug 2003 15:47:29 -0700 (PDT) [thread overview]
Message-ID: <20030814224729.32404.qmail@web14911.mail.yahoo.com> (raw)
In-Reply-To: <1060898658.13316.4.camel@gaston>
--- Benjamin Herrenschmidt <benh@kernel.crashing.org>
wrote:
> 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.
>
Putting the EDID data into the RAM copy will never
work the case where there are multiple cards since
there is only one copy of the ROM in low RAM.
Personally I'd just like to ignore the boot VROM and
do everything in the Radeon driver code. But ATI won't
give out detailed info on how to read EDID or reset
the card with C code from the driver. So instead we
end up with the idiotic x86 emulator and doing INT10's
in simulated real mode.
Maybe someone with more leverage can coax this info
out of them.....
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-------------------------------------------------------
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:47 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
2003-08-14 22:47 ` Jon Smirl [this message]
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=20030814224729.32404.qmail@web14911.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--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).