linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Re: Ethernet issues with lite5200 board from linux-2.6.31
       [not found] ` <d1f76ba30911300150g10c1382clb2958245ebf94362@mail.gmail.com>
@ 2009-11-30 15:59   ` Grant Likely
  2009-12-01  5:48     ` Yogesh Chaudhari
  2009-12-03  4:14     ` Yogesh Chaudhari
  0 siblings, 2 replies; 3+ messages in thread
From: Grant Likely @ 2009-11-30 15:59 UTC (permalink / raw)
  To: Yogesh Chaudhari
  Cc: Robin Gareus, rt-users, Fernando Lopez-Lezcano, Peter Zijlstra,
	Frank Rowand, Philippe Reynes, Mark Knecht, LKML, Steven Rostedt,
	Sven-Thorsten Dietrich, linuxppc-dev, Clark Williams, Darren Hart,
	Will Schmidt, Jon Masters, John Kacur, Ingo Molnar, Jan Blunck,
	Gregory Haskins

On Mon, Nov 30, 2009 at 2:50 AM, Yogesh Chaudhari <mr.yogesh@gmail.com> wro=
te:
> Hello,
> =A0 =A0 =A0 =A0 I am running linux kernel with rt patch on embedded board
> based on lite5200 eval board. From linux-2.6.31 release, in which the
> mdio patch has gone inside, =A0the fec ethernet does not come up on this
> board. I get the following message at startup:
> mpc52xx MII bus: probed
> mdio_bus f0003000: error probing PHY at address 1
>
>
> After the bootup if I try to do a ifconfig I get the message:
> net eth2: of_phy_connect failed
>
>
> If I change the value of reg in dts file (lite5200.dts) to 0 then this
> ethernet comes up. However upto this kernel version, this was not
> required.
>
> Ethernet does not come up on board with original lite5200.dts file

Is your board based on the Lite5200 or the Lite5200B?  The phys are at
different addresses on those two revisions of the board.  There is a
different .dts file for each board.

> phy0: ethernet-phy@1 {
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D=
 <1>;
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>
> Ethernet comes up on board with this change
> phy0: ethernet-phy@1 {
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D=
 <0>;
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};

Some PHYs treat address 0 as the 'broadcast' address.  You need to
fill in this field (and modify the ethernet-phy@<address> node name)
to reflect the address that your phy is actually at.

g.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ethernet issues with lite5200 board from linux-2.6.31
  2009-11-30 15:59   ` Ethernet issues with lite5200 board from linux-2.6.31 Grant Likely
@ 2009-12-01  5:48     ` Yogesh Chaudhari
  2009-12-03  4:14     ` Yogesh Chaudhari
  1 sibling, 0 replies; 3+ messages in thread
From: Yogesh Chaudhari @ 2009-12-01  5:48 UTC (permalink / raw)
  To: Grant Likely
  Cc: Robin Gareus, rt-users, Fernando Lopez-Lezcano, Peter Zijlstra,
	Frank Rowand, Philippe Reynes, Mark Knecht, LKML, Steven Rostedt,
	Sven-Thorsten Dietrich, linuxppc-dev, Clark Williams, Darren Hart,
	Will Schmidt, Jon Masters, John Kacur, Ingo Molnar, Jan Blunck,
	Gregory Haskins

Hello Grant,

2009/11/30 Grant Likely <grant.likely@secretlab.ca>:
> On Mon, Nov 30, 2009 at 2:50 AM, Yogesh Chaudhari <mr.yogesh@gmail.com> w=
rote:
>> Hello,
>> =A0 =A0 =A0 =A0 I am running linux kernel with rt patch on embedded boar=
d
>> based on lite5200 eval board. From linux-2.6.31 release, in which the
>> mdio patch has gone inside, =A0the fec ethernet does not come up on this
>> board. I get the following message at startup:
>> mpc52xx MII bus: probed
>> mdio_bus f0003000: error probing PHY at address 1
>>
>>
>> After the bootup if I try to do a ifconfig I get the message:
>> net eth2: of_phy_connect failed
>>
>>
>> If I change the value of reg in dts file (lite5200.dts) to 0 then this
>> ethernet comes up. However upto this kernel version, this was not
>> required.
>>
>> Ethernet does not come up on board with original lite5200.dts file
>
> Is your board based on the Lite5200 or the Lite5200B? =A0The phys are at
> different addresses on those two revisions of the board. =A0There is a
> different .dts file for each board.
>
>> phy0: ethernet-phy@1 {
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =
=3D <1>;
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>>
>> Ethernet comes up on board with this change
>> phy0: ethernet-phy@1 {
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =
=3D <0>;
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>
> Some PHYs treat address 0 as the 'broadcast' address. =A0You need to
> fill in this field (and modify the ethernet-phy@<address> node name)
> to reflect the address that your phy is actually at.

This change in reg value was not required till 2.6.31. It is only
after this version that the change is needed. Is there some change in
31 that makes this change mandatory?

>
> g.
>



--=20
DREAM IT, CODE IT

"CODITO, ERGO SUM"
"I CODE, THEREFORE I AM"

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ethernet issues with lite5200 board from linux-2.6.31
  2009-11-30 15:59   ` Ethernet issues with lite5200 board from linux-2.6.31 Grant Likely
  2009-12-01  5:48     ` Yogesh Chaudhari
@ 2009-12-03  4:14     ` Yogesh Chaudhari
  1 sibling, 0 replies; 3+ messages in thread
From: Yogesh Chaudhari @ 2009-12-03  4:14 UTC (permalink / raw)
  To: LKML
  Cc: Robin Gareus, rt-users, Fernando Lopez-Lezcano, Peter Zijlstra,
	Frank Rowand, Philippe Reynes, Mark Knecht, Steven Rostedt,
	Sven-Thorsten Dietrich, Clark Williams, Darren Hart, Will Schmidt,
	Jon Masters, John Kacur, Ingo Molnar, Jan Blunck, Gregory Haskins,
	linuxppc-dev

2009/11/30 Grant Likely <grant.likely@secretlab.ca>:
> On Mon, Nov 30, 2009 at 2:50 AM, Yogesh Chaudhari <mr.yogesh@gmail.com> w=
rote:
>> Hello,
>> =A0 =A0 =A0 =A0 I am running linux kernel with rt patch on embedded boar=
d
>> based on lite5200 eval board. From linux-2.6.31 release, in which the
>> mdio patch has gone inside, =A0the fec ethernet does not come up on this
>> board. I get the following message at startup:
>> mpc52xx MII bus: probed
>> mdio_bus f0003000: error probing PHY at address 1
>>
>>
>> After the bootup if I try to do a ifconfig I get the message:
>> net eth2: of_phy_connect failed
>>
>>
>> If I change the value of reg in dts file (lite5200.dts) to 0 then this
>> ethernet comes up. However upto this kernel version, this was not
>> required.
>>
>> Ethernet does not come up on board with original lite5200.dts file
>
> Is your board based on the Lite5200 or the Lite5200B? =A0The phys are at
> different addresses on those two revisions of the board. =A0There is a
> different .dts file for each board.
>
>> phy0: ethernet-phy@1 {
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =
=3D <1>;
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>>
>> Ethernet comes up on board with this change
>> phy0: ethernet-phy@1 {
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =
=3D <0>;
>> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>
> Some PHYs treat address 0 as the 'broadcast' address. =A0You need to
> fill in this field (and modify the ethernet-phy@<address> node name)
> to reflect the address that your phy is actually at.
>
> g.
>
 I have tried the same with the latest kernel both with and without
rt, but with the same end result. I have checked that the mpc52xx fec
driver was changed from 2.6.31 version but I am not able to point
where this error is coming up from and how changing the reg value in
dts (which is not required till previous versions) is solving this.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-12-03  4:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <d1f76ba30911300038w272578dfx9adb116bde493e00@mail.gmail.com>
     [not found] ` <d1f76ba30911300150g10c1382clb2958245ebf94362@mail.gmail.com>
2009-11-30 15:59   ` Ethernet issues with lite5200 board from linux-2.6.31 Grant Likely
2009-12-01  5:48     ` Yogesh Chaudhari
2009-12-03  4:14     ` Yogesh Chaudhari

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).