From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp8.wanadoo.fr (smtp8.wanadoo.fr [193.252.22.23]) by ozlabs.org (Postfix) with ESMTP id D700867A6D for ; Sun, 6 Mar 2005 07:44:24 +1100 (EST) Date: Sat, 5 Mar 2005 21:32:54 +0100 To: Sven Luther Message-ID: <20050305203254.GB30151@pegasos> References: <41F6E0E1.6000803@mvista.com> <20050224082508.GA30005@pegasos> <421DF2B8.6040007@mvista.com> <20050224160411.GA11197@pegasos> <20050224172420.GA6932@xyzzy> <20050305192752.GA28491@pegasos> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <20050305192752.GA28491@pegasos> From: Sven Luther Cc: Nicolas DET , linuxppc-embedded@ozlabs.org Subject: Re: [PATCH][PPC32] mv64x60 updates List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, Mar 05, 2005 at 08:27:52PM +0100, Sven Luther wrote: > On Thu, Feb 24, 2005 at 10:24:20AM -0700, Dale Farnsworth wrote: > > 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. > > What is the status of this with regard to the 2.6.11 mainline kernel ? > > > > 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 > > I guess i need to look there, as in mainline 2.6.11, there doesn't seem to be > direct related code between the ppc specific mv64x60 stuff, and the mips > related ethernet one. Ok, i think that did it, and i have a 200kb diff against 2.6.11 :) Many of those are just 64340-> 643xx replacements though. What are your plans for mainline inclusion of the rest of those, and is it ok to work directly with your stuff ? Do you have any experimental or dangerous parts in the above ? And did you ever get the gigabit ethernet port working on a powerpc board ? Or are there some Kconfig parts i have missed ? Friendly, Sven Luther