MVME 5100
???
So would it be better to use the CHRP settings to build a kernel for the MVME5100 ?
Torsten
-----Ursprungliche Nachricht-----
Von: Gabriel Paubert [SMTP:[email protected]]
Gesendet am: Montag, 18. Dezember 2000 19:08
An: Matt Porter
Cc: Torsten Rissel; Linuxppc-Embedded (E-Mail)
Betreff: Re: MVME 5100
Quoted 10 lines · Matt Porter
Quoted 3 lines
On the MVME2400 (and older Raven/Falcon based boards) the config space by default is at
0x80000cf8and0x8000cfc. Does it mean that on the MVME5100, the Hawk is reprogrammed by PPCBUG to look like a CHRP system ?Yes...and Yes. :) The only thing the newer MCG boards really do (correctly) that looks like a PReP system is the disk booting mechanism.
BTW, the MVME2100 (8240/Universe II board) is put in map B for a CHRP map as well.
Ok, fine. It means that my code to reprogram the Raven/Hawk on 2[467]xx just makes things more uniform. I still don't like the fact that the DMA is offset, though (unless it's a residual data bug, and map B on 106/107 does not have this DMA offset).
Regards,
Gabriel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 3 lines · Torsten Rissel
???
So would it be better to use the CHRP settings to build a kernel for the MVME5100 ?
Not necessarily. What I did on my machines was to put them in CHRP mode by reprogramming the Raven or the Hawk, but I essentially used a common kernel (just adding a powerplus boolean in some cases, this is however not the right solution). Try the CHRP version but you might still run into problems. I don't trust residual data, the problem you have is most likely the missing interrupt routing information thing.
Try to find what the network interrupts are on the MVME5100 and add the data in the tables in prep_pci.c, since Motorola does not provideeeee this vital information.
Regards,
Gabriel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/