On Wed, 4 Feb 2004, Richard Smith wrote:

quoted

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:

quoted

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?

Atyfb reads them from the registers.

quoted

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?

1002:4c4d

Any idea what he had to do?  Most of DM's code seems to deal with

IIRC, programming an extra shadow register.

makeing it work properly with a LCD.  Right now I just have a CRT hooked
up.  LCD will comes later.

quoted

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?

I think 2.4 is the safest. I don't know whether James' tree already contains
all Mobility support from 2.4.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


-------------------------------------------------------
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