Re: URGENT: status of atyfb

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

> Hi, I do not have any information or hardware about PPC. Should it own 
> something like OpenFirmware? In this case it is possible to read clock 
> information from this.

On some models, yes, on some no. Older machines have a firmware that
won't tell you anything, the MacOS driver back then was hard coding the
values.

Anyway, the clocks are ok, apparently (maybe not the engine one though,
see later), the problem was that the DLL magic was reverted for the
LT-G, plus some minor issues with the driver blowing up on non-BIOS
machines that I can fix.

The engine tends to lockup quickly though, I'll do experiments.

> I found, that we change a little behaviour. Please give a try for this 
> patch...

Your patch seem to address the DLL issue, I did that too, fixes the display,
I'll toy around and let you know.

Also, when just dropping the existing driver into the current linus tree, the
cursor code is blowing up, I don't know why yet, I suppose some changes to the
common code in the fbdev tree. I'll have a look.

I really want this new driver to be sent upstream ASAP. What I may do is once
I get it working well enough, I'll send it to andrew for the -mm tree and
leave it there for a while to get it properly tested.

Ben.



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com