[RFC] How to allow selecting mv643xx_eth on Pegasos again

[RFC] How to allow selecting mv643xx_eth on Pegasos again

[Gabriel Paubert]

On Thu, Jan 08, 2009 at 11:53:10PM -0600, Matt Sealey wrote:
> Lennert Buytenhek wrote:
>> On Thu, Jan 08, 2009 at 11:38:33PM -0600, Matt Sealey wrote:
>>
>> On this topic, I sent a patch to linuxppc-dev@ some time ago that moves
>> the mv643xx_eth SRAM window programming code from the Pegasos platform
>> code to the mv643xx_eth driver, and adds a couple of fields to the
>> mv643xx_eth platform data that lets you pass the sram addresses/sizes
>> in.  Since I don't have the hardware I haven't been able to test it,
>> but it would be nice if someone could.
>
> It seems to work. However it's still static stuff in some platform  
> driver, which I don't really like. pegasos_eth.c is really a holdover  
> from the very early days of ppc->powerpc architecture port, where they  
> insisted that we do detection that way (and fudge it based on host  
> controller PCI ID)
>
> The Pegasos device tree is so screwed up, you could never gain the  
> information you need from it. And times have changed..

I just tried to compile a very recent kernel for my Pegasoi, and
I can no more select the MV643XX_ETH driver. The root cause is that
PPC_MULTIPLATFORM has been removed. There are several possibilities:

1) remove simply the PPC_MULTIPLATFORM and let it depends on PPC32

2) replace PPC_MULTIPLATFORM && PPC32 by 6xx which is apparently the
   blessed way of doing this. But I dislike a 6xx condition in anything
   outside arch/powerpc.

3) add a select statement for MV64X60 in CHRP. It will bring in more
   code and would probably need an OF node for the system controller.
   I suspect that the mv64x60 pic and i2c are not wired on Pegasos.

Pick your poison...

While at it, I'm also going to remove the last remnants of MV64360
since it is never selected anywhere (replaced by MV64X60).  

	Regards,
	Gabriel

P.S.: this is not sufficient, after this the driver crashes at initialization
but that's a separate patch, that has to do with the dma mapping interface.

Re: [RFC] How to allow selecting mv643xx_eth on Pegasos again

[Simon Richter]

Hi,

I just tried upgrading my PegasosII to 2.6.29, and found that the Marvell
driver shows two Ethernet ports now, one with a MAC address ending in
...:de:ad:01 (which is the port that is not wired to the outside), and the
other one with 00:00:00:00:00:00.

I think some sort of Pegasos specific hack is needed.

   Simon

Re: [RFC] How to allow selecting mv643xx_eth on Pegasos again

[Gabriel Paubert]

On Thu, May 14, 2009 at 10:59:02AM +0200, Simon Richter wrote:
> Hi,
> 
> I just tried upgrading my PegasosII to 2.6.29, and found that the Marvell
> driver shows two Ethernet ports now, one with a MAC address ending in
> ...:de:ad:01 (which is the port that is not wired to the outside), and the
> other one with 00:00:00:00:00:00.
> 
> I think some sort of Pegasos specific hack is needed.

For that specific problem othere is the patch that I submitted to this 
mailing list, which was merged early into 2.6.30.

	Gabriel