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)
Kernel bootup mesages on 2.6.12 for eth initialisation :
[ 1.706436] eth0: Gianfar Ethernet Controller Version 1.1,
00:01:af:07:9b:8a
[ 1.713769] eth0: Running with NAPI disabled
[ 1.718137] eth0: 64/64 RX/TX BD ring size
[ 1.722483] eth1: Gianfar Ethernet Controller Version 1.1,
fd:e4:75:9d:72:6f
[ 1.729812] eth1: Running with NAPI disabled
[ 1.734180] eth1: 64/64 RX/TX BD ring size
[ 1.738521] eth2: Gianfar Ethernet Controller Version 1.1,
6f:74:3d:2f:64:65
[ 1.745851] eth2: Running with NAPI disabled
[ 1.750218] eth2: 64/64 RX/TX BD ring size
On 2.4.20 it is the same :
eth0: Gianfar Ethernet Controller Version 1.0, 00:01:af:07:9b:8a
eth0: Running with NAPI disabled
eth0: 64/64 RX/TX BD ring size
eth1: Gianfar Ethernet Controller Version 1.0, fd:e4:75:9d:72:6f
eth1: Running with NAPI disabled
eth1: 64/64 RX/TX BD ring size
eth2: Gianfar Ethernet Controller Version 1.0, 6f:74:3d:2f:64:65
eth2: Running with NAPI disabled
eth2: 64/64 RX/TX BD ring size
I am able to ping and use telnet,ftp etc when booted from 2.4.20 but ping,
telnet,ftp, don't work eventhough i use same ramdisk in both the cases.
ifconfig shows card is up in 2.6.12 too.
Regards,
Prashant
______________________________________________________________________
From: Kumar Gala <hidden> Date: 2006-08-11 04:11:05
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
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 [off-list ref]
08/11/2006 09:40 AM
To
Prashant Yendigeri [off-list ref]
cc
linuxppc-embedded@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
______________________________________________________________________
______________________________________________________________________
From: Kumar Gala <hidden> Date: 2006-08-11 12:37:58
On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote:
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.
Are you doing this on a custom board? If so what is the PHY address
for the Marvell phy you are using?
- k
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 [off-list ref]
08/11/2006 09:40 AM
To
Prashant Yendigeri [off-list ref]
cc
linuxppc-embedded@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:
quoted
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
______________________________________________________________________
______________________________________________________________________
Hi,
This is a standard board designed by GDA technologies Inc.
(www.gdatech.com) and eth on 2.4.20 works very much.
U-Boot 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=>
-prashant
Kumar Gala [off-list ref]
Sent by:
linuxppc-embedded-bounces+prashant.yendigeri=lntinfotech.com@ozlabs.org
08/11/2006 06:07 PM
To
Prashant Yendigeri [off-list ref]
cc
linuxppc-embedded@ozlabs.org
Subject
Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote:
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.
Are you doing this on a custom board? If so what is the PHY address
for the Marvell phy you are using?
- k
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 [off-list ref]
08/11/2006 09:40 AM
To
Prashant Yendigeri [off-list ref]
cc
linuxppc-embedded@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:
quoted
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
______________________________________________________________________
______________________________________________________________________
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
______________________________________________________________________
______________________________________________________________________
From: Matthew McClintock <hidden> Date: 2006-08-11 14:30:41
On Fri, 2006-08-11 at 18:13 +0530, Prashant Yendigeri wrote:
Hi,
This is a standard board designed by GDA technologies Inc.
(www.gdatech.com) and eth on 2.4.20 works very much.
I used a 8540 GDA board once upon a time and all I needed to do was to
change the PHY address. Lookat your 2.4 source and determine what the
correct value is and double check.
-Matthew
-----Original Message-----
From:=20
linuxppc-embedded-bounces+dai.haruki=3Dfreescale.com@ozlabs.org=20
[mailto:linuxppc-embedded-bounces+dai.haruki=3Dfreescale.com@ozl
abs.org] On Behalf Of Kumar Gala
Sent: Friday, August 11, 2006 7:38 AM
To: Prashant Yendigeri
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6=20
: differentoutputs
=20
=20
On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote:
=20
quoted
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 =20
with Marvell phy enabled.
=20
=20
Are you doing this on a custom board? If so what is the PHY address =20
for the Marvell phy you are using?
=20
- k
=20
quoted
Kernel boot messages :
[ 2.296555] Gianfar MII Bus: probed
[ 2.301789] eth0: Gianfar Ethernet Controller Version 1.2, =20
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, =20
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:=20
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 [off-list ref]
08/11/2006 09:40 AM
To
Prashant Yendigeri [off-list ref]
cc
linuxppc-embedded@ozlabs.org
Subject
Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different =20
outputs
On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote:
quoted
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
=20