Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
Prashant Yendigeri
Prashant.Yendigeri at lntinfotech.com
Thu Aug 17 19:33:30 EST 2006
Hi,
This is what i am getting from u-boot print messages :
U-Boot 1.1.0(pq3-20040423-r1) (May 5 2006 - 08:56:54)
Freescale PowerPC
Core: E500, Version: 2.0, (0x80200020)
System: 8540, Version: 2.0, (0x80300020)
Clocks: CPU: 660 MHz, CCB: 264 MHz, DDR: 132 MHz, LBC: 66 MHz
L1 D-cache 32KB, L1 I-cache 32KB enabled.
Board: Freescale EVAL8540 Board
CPU: 660 MHz
CCB: 264 MHz
DDR: 132 MHz
LBC: 66 MHz
L1 D-cache 32KB, L1 I-cache 32KB enabled.
I2C: ready
DRAM: 256 MB
FLASH: 8 MB
L2 cache enabled: 256KB
In: serial
Out: serial
Err: serial
Net: Freescale ENET0: PHY is Marvell 88E1011S (1410c62)
Freescale ENET1: PHY is Marvell 88E1011S (1410c62)
Freescale ENET2: PHY is Intel LXT971A (1378e2)
Freescale ENET0, Freescale ENET1, Freescale ENET2
Hit any key to stop autoboot: 0
MPC8540EVAL=>
MPC8540EVAL=>
This seems to me it is a old board from GDATECH . Data sheet not available
for this.
-prashant
Ho Jeffrey-r26191 <r26191 at freescale.com>
08/12/2006 06:32 AM
To
"'Prashant Yendigeri'" <Prashant.Yendigeri at lntinfotech.com>, Kumar Gala
<galak at kernel.crashing.org>
cc
linuxppc-embedded at ozlabs.org
Subject
RE: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
Hi
>>>>[ 34.041809] 0:00 not found
SIOCSIFFLAGS: No[ 34.044526] eth0: Could not attach to PHY
such device
SIOCSIFFLAGS: No such device
>>>>> eth0: PHY is Generic MII (ffffffff)
_______________________________________________________
Can you quickly check if you have the right phy id written in your
platform file for your board?
Regards,
Jeffrey Ho
Freescale Semiconductor HK Ltd
________________________________
From:
linuxppc-embedded-bounces+r26191=freescale.com at ozlabs.org
[mailto:linuxppc-embedded-bounces+r26191=freescale.com at ozlabs.org] On
Behalf Of Prashant Yendigeri
Sent: Friday, August 11, 2006 7:21 PM
To: Kumar Gala
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: Gianfar eth driver on 8540 ppc - for 2.4 and
2.6 : different outputs
Hi,
Downloaded 2.6.16.26 and booted up and got this :
/ # ifconfig eth0 172.28.8.254 up
[ 34.034596] 0:00 not found
[ 34.037330] eth0: Could not attach to PHY
[ 34.041809] 0:00 not found
SIOCSIFFLAGS: No[ 34.044526] eth0: Could not attach to
PHY
such device
SIOCSIFFLAGS: No such device
I had enabled all the PHY devices in .config and also
tried only with Marvell phy enabled.
Kernel boot messages :
[ 2.296555] Gianfar MII Bus: probed
[ 2.301789] eth0: Gianfar Ethernet Controller Version
1.2, 00:01:af:07:9b:8a
[ 2.309039] eth0: Running with NAPI disabled
[ 2.313307] eth0: 64/64 RX/TX BD ring size
[ 2.318498] eth1: Gianfar Ethernet Controller Version
1.2, 00:00:00:00:72:6f
[ 2.325738] eth1: Running with NAPI disabled
[ 2.330006] eth1: 64/64 RX/TX BD ring size
[ 2.335198] eth2: Gianfar Ethernet Controller Version
1.2, 6f:74:3d:2f:64:65
[ 2.342377] eth2: Running with NAPI disabled
[ 2.346662] eth2: 64/64 RX/TX BD ring size
[ 2.351586] Marvell 88E1101: Registered new driver
[ 2.357010] Davicom DM9161E: Registered new driver
[ 2.362443] Davicom DM9131: Registered new driver
[ 2.367775] Cicada Cis8204: Registered new driver
[ 2.373136] LXT970: Registered new driver
[ 2.377794] LXT971: Registered new driver
[ 2.382461] QS6612: Registered new driver
Regards,
Prashant
Kumar Gala <galak at kernel.crashing.org>
08/11/2006 09:40 AM
To
Prashant Yendigeri
<Prashant.Yendigeri at lntinfotech.com>
cc
linuxppc-embedded at ozlabs.org
Subject
Re: Gianfar eth driver on 8540 ppc - for
2.4 and 2.6 : different outputs
On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote:
>
> Hi,
>
> The gianfar driver of 2.6.12 and 2.4.20 give different
outputs on
> the same PPC 8540 board.
>
> What could be the reason ?
>
> Output on 2.4.20 :
> /root # ifconfig eth0 172.28.8.254 up
> eth0: PHY is Marvell 88E1011S (1410c62)
> eth0: Auto-negotiation done
> eth0: Half Duplex
> eth0: Speed 10BT
> eth0: Link is up
>
> Output on 2.6.12
> / # ifconfig eth0 172.28.8.254 up
> eth0: PHY is Generic MII (ffffffff)
It looks like your 2.6.12 kernel isn't handling the PHY
correctly.
I'd recommend upgrading to something newer which has the
phylib
(can't remember which 2.6 that went into).
- kumar
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060817/a101e3dc/attachment.htm
More information about the Linuxppc-embedded
mailing list