mv64x60 updates

Nicolas DET det.nicolas at
Mon Mar 7 06:48:01 EST 2005

Hello Sven,

On 06/03/2005, you wrote:

> Ah, i guess that was the missing bit. Basically i need to set MV64360 for
> my board, but since it is a generic PPC_CHRP, how is that supposed to
> work ?  
> Could you send me maybe a list of files which need merging yet, compared
> to 2.6.11 ? I guess it just doesn't work because i am missing pieces.

I fixed that here.
TheKconfig issue is really minor compared to the rest :-)

>> > Anyway, how do you probe for the chip ? On the pegasos we used to map
>> > on the marvell pci id :
>> > 
>> >   0000:00:00.0 Host bridge: Marvell Technology Group Ltd.
>> > MV64360/64361/64362   System Controller (rev 03)
>> > 
>> > too bad Marvell didn't do the logical thing and made the ethernet port
>> > appear as separated devices on a third internal pci bus.
>> The mv643xx_eth probe is dependent on having the appropriate
>> platform device entry.  See eth0_device and mv64x60_add_pds() in
>> arch/ppc/syslib/mv643x60.c .

> The pegasos has the mv64360 registers mapped at 0xf1000000, and the ports
> (only port1 is wired though) mapped at interrupt 9, shared with other
> devices. I guess that would be the only real difference with the other
> currently supported hardware, right ? 

Yeah, and also, Pegasos II kernel shouldn't call all the chipset init call
which has been added.
Pegasos II chipset init is done by the OFW. OSs kernel shouldn't have to
touch it much.

> Will look at the above mentioned files and function and try to enable it.

I already patch a bit the kernel. However, enabling new Marvell code means
not booting anymore ATM.
I'm trying to find a way to patch the current source, without breaking
Katana & friends support.

The smartest could be to move all unneeded/board specific code somewhere
else (chipset init...) and to keep ony the minimal (only
platform_get_resource() realted stuff), in arch/ppc/syslib/mv64x60*

Nicolas DET
MorphOS & Linux developer

More information about the Linuxppc-dev mailing list