On Thu, Feb 24, 2005 at 04:04:11PM +0000, Sven Luther wrote: > > >I am a bit bewildered by what you are doing here. How does this mv64x60 > > >code relate to the mv643xx_eth driver from the mips folk ? > > [...] > > On Thu, Feb 24, 2005 at 08:28:56AM -0700, Mark A. Greer wrote: > > has spent a lot of time making it work on both MIPS and PPC. The code > > you see in the mv64x60.c file is a part of that. I believe that Dale's > > Ok, so the code in question is in addition to the existing driver from the > mips guys and works with it ? I had the impression that it was a separate > driver development or something.
The code in mv64x60.c is related to but separate from the ethernet driver. It is platform-specific code that passes register addresses, irqs, mac addrs, phy addrs, etc. to the arch-agnostic ethernet driver. All of my changes to the mv643xx ethernet driver have been posted to LKML or the netdev list. I have removed all arch-specific code from the ethernet driver itself. > Ok. Do you know if Dale's patches are available separatedly while they are not > yet in mainline, so Nicolas Det can work on them and make sure they also work > on the Pegasos board, which is not an embedded board but from the chrp See bk://dfarnsworth.bkbits.net/linux-2.5-mv643xx-enet > lineage. Nicolas already did some mv643xx ethernet driver work last summer, > but apparently had trouble integrating this in the mainline kernel, and it I'm sorry I wasn't aware of Nicolas' work on the driver. > seems his work has now been redone by Dale or something. Do you know who the > right person to communicate with about this would be ? The MIPS folk didn't > reply to any of our mails about this subject. Sounds familiar. Fortunately, Jeff Garzik picked up my changes. I would appreciate feedback from you or Nicolas on the current driver. Thanks, -Dale