From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outmx018.isp.belgacom.be (outmx018.isp.belgacom.be [195.238.4.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 8039BDDE36 for ; Thu, 11 Jan 2007 01:55:28 +1100 (EST) Received: from outmx018.isp.belgacom.be (localhost [127.0.0.1]) by outmx018.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id l0AEsiFv025138 for ; Wed, 10 Jan 2007 15:54:45 +0100 (envelope-from ) Message-ID: <45A4FDAF.8020909@246tNt.com> Date: Wed, 10 Jan 2007 15:52:31 +0100 From: Sylvain Munaut MIME-Version: 1.0 To: Andrea Galbusera Subject: Re: Ethernet fails on MPC5200 based target References: <1168439212.5271.70.camel@localhost.localdomain> In-Reply-To: <1168439212.5271.70.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi andrea, Could you tell me exactly what kernel you use from me ? (a commit id would do) And did you write your own platform file ? Maybe some things (like xlb pipelining, cache snooping, ...) is not properly setup in you platform support code ? Or maybe since the ethernet code currently only "knows" about the intel phy, something is wrong in the "generic" phy code included in the driver itself. Sylvain Andrea Galbusera wrote: > Hi all, > > I have a problem with ethernet on my MPC5200 based board. > > Ethernet is failing on my target with both 2.6.16.11-rt18 from Freescale > BSP (based on the ltib tool) and 2.6.16-rc1-g7cdaf877 from Sylvain > Munaut's git tree. On the opposite, it works fine with a relatively old > (April 2006) 2.6.16 from Denx. > > What I see is that network is not working (corruption occur). I use a > ramdisk rootfs to boot and I get an up-and-running system. Then, if I > ping it from a remote host I get the following errors: > > >> ping 192.168.0.183 >> PING 192.168.0.183 (192.168.0.183) 56(84) bytes of data. >> 64 bytes from 192.168.0.183: icmp_seq=1 ttl=64 time=8.00 ms >> 64 bytes from 192.168.0.183: icmp_seq=2 ttl=64 time=0.188 ms >> wrong data byte #20 should be 0x14 but was 0xc0 >> #8 8 9 a b c d e f 10 11 12 13 c0 15 16 17 18 19 1a 1b 1c 1d 1e >> 1f 20 21 22 23 24 25 26 27 >> #40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 >> 64 bytes from 192.168.0.183: icmp_seq=3 ttl=64 time=0.217 ms >> 64 bytes from 192.168.0.183: icmp_seq=5 ttl=64 time=0.216 ms >> wrong data byte #20 should be 0x14 but was 0x0 >> #8 8 9 a b c d e f 10 11 12 13 0 15 16 17 18 19 1a 1b 1c 1d 1e 1f >> 20 21 22 23 24 25 26 27 >> #40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 >> 64 bytes from 192.168.0.183: icmp_seq=6 ttl=64 time=0.187 ms >> > > Since my target is heavily based on the Lite5200 I tryed all three > kernels on the Lite5200 too and they all show working ethernet. > > This may suggest something related with the different phy hardware, but > consider that the kernel from Denx works fine on it! > My target hardware uses MPC5200B CPU and AMD NetPhy AM79C874 for the > network phy. > > Can you suggest what source file may be responsible for this behaviour > in order to dig the trees and maybe, hopefully, fix the problem? I tryed > a first diffing between the Denx and the Freescale trees (this last one > being mostly based on Sylvain's patches) but I can't figure out any > reasonable answer. > > Consider I can't unfortunately switch to 2.6.16 from Denx because it > does not support ATA/IDE that I need; also switching to the new powerpc > architecture is not an option at moment, since it would require changes > to the system at whole. > > TIA and let me know if you need more details > > >