On Tue, 3 Feb 2004, Richard Smith wrote:
quoted
new untested hardware booting a half-ass videobios running an unknown
driver. Gee... wonder why it dosen't work? *grin*
Geert Uytterhoeven wrote:
Indeed, atyfb needs BIOS (or OpenFirmware) initialization. It has
How much? Are things like the ammount and type of RAM autodetected or just read from registers that the BIOS is supposed to set?
initialization code for RAGE XL, though.
Any idea how different the RAGE XL is from the M1? I know they are both Mach64 but how consistent are the registers across all of the Mach64 chips?
My Vaio Z600TEK (Z505 in US/JP) has a M1. It works with atyfb in recent 2.4,
but it took Daniël Mantione quite a bit of work to make it work on this
particular machine...
What device ID is your M1?
Any idea what he had to do? Most of DM's code seems to deal with makeing it work properly with a LCD. Right now I just have a CRT hooked up. LCD will comes later.
Let's say atyfb in 2.4 works on most M1s these days.
So which one should I work with? 2.4 or 2.6 with fbdiff?
--
Richard A. Smith
rsmith@bitworks.com
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn