Re: [Linux-fbdev-devel] Re: pm3fb and new motherboard ...

[Romain D. <do...@ir...>]

Sven wrote:

> I don't really understand what happens here, but adding an off:0: did make the
> console appear on the first head again. (BTW, what hinted me to this is the
> fact that pm3fb was reporting Appian J2000 head 2, so pm3fb can recognize the
> correct head number, just doesn't use it to attribute it to the fbs.)

No, fb are registered in the order they are found, i.e. the order
of the "pci_find_device()" function. I have no idea how this
one behave with regards to motherboard.

You should be able to use the "pciid" option to put things back
in order. i.e. "pciid:0:1:0:1,pciid:1:1:0:2" (assuming pci bus
& device number are 1 & 0) *should* restore the old behavior.

The name is not used at all, it's only to make the user
feel better, with the board name in dmesg ;-) Seriously,
it's only used to try to get proper timings for the memory.

> BTW, is ruby supposed to work ? I compiled yesterday a 2.5.1 kernel + ruby,
> and after booting into it, it hangs immediately at the begining (4-5th line of
> the kernel log). 2.5.2 + vesafb but no ruby works fine though.

No, it's not. I never managed to get Ruby working on my box,
so I can't even try pm3fb/ruby. When ruby start working OK
on PPC, I might try to make pm3fb works in it, if I find
the time.

-- 
DOLBEAU Romain               | The Gods made Heavy Metal                
ENS Cachan / Ker Lann        |     and it's never gonna die             
Thesard IRISA / CAPS         |           -- Manowar,                    
dol...@cl...    |    'The Gods made Heavy Metal'