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.
Yup, but at least it works for single cards, and that
helps a lot of users until radeonfb can do better
Personally I'd just like to ignore the
--- Benjamin Herrenschmidt [EMAIL PROTECTED]
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
On Thu, 2003-08-14 at 18:00, Jon Smirl wrote:
--- Benjamin Herrenschmidt [EMAIL PROTECTED]
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,
--- Benjamin Herrenschmidt [EMAIL PROTECTED]
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
--- Alex Deucher [EMAIL PROTECTED] wrote:
2) access ROM directly instead of relying on copy
in low RAM. This allows multiple cards. Required
MPP_TB_CONFIG fix in driver.
Is this patch necessary for xfree86? It may address
some of the issues
in the email threads I sent out yesterday
I haven't tried multiple radeon cards, but I seem to recall several
people having this problem right around when 4.3.0 was released. I
don't think a proper fix ever went in and I think the issue was to be
revisited later. I don't know if it's needed anymore or not.
Alex
--- Jon Smirl [EMAIL
