Re: accessing ROM on Rage 128 chips in aty128fb

[Martin Murray <mmurray@deepthought.org>]

Jon, Thank you for your reply.

>  > Why does the linux PCI code not set up a mapping for the ROM
>  > automatically?
>
> It expects the BIOS to do it. You can force it to try with the option
> "pci=rom"

This worked and I was able to access the BIOS. Is there a method to ask
the pci code to do this from a driver, if pci=rom was not used?

> Assuming this is the active grahpics card, then you should be able to
> access the rom via the legacy VGA address range 0xc0000...0xc7fff which
> should be shown in /proc/iomem.

This worked, I realized that I was chasing the wrong bug - the code to
find the BIOS was looking for a "R128" signature, where my mobile Rage 128
has an "M3" signature. I patched the driver to search for "M3" as well as
"Rage 128" and it properly found the BIOS and loaded the pll information.
(The mobile version of the Rage 128 is called the Rage M3 Mobility, but it
is still a Rage 128.) Who do I submit this change to?

Unfortunately, the display is still garbage even after loading the correct
information from the BIOS. I have not been able to contact the aty128fb
author, does anyone have any suggestions? My next step is to compare how
the aty128fb driver initializes the display to the way the X4.3.0 server
does, however, this seems very tedious.

Thank you, Martin Murray