Hi Vitaly,
I was pointed in the direction of message chain "Fixed PHY problems" for
interfacing a fixed PHY to a 83xx UEC. Could you please forward on the
patch you mentioned in the trail?
Any ideas if the implementation succeeded in the end?
Christian Hammond
NCSG Applications Engineer
Tel: +44 1355 355962
Fax: +44 1355 261790
Freescale Semiconductor
Kelvin Industrial Estate
East Kilbride
Glasgow G75 0TG
United Kingdom
On Sat, 2007-05-19 at 15:42 +0100, Hammond Christian-r55079 wrote:
Hi Vitaly,
I was pointed in the direction of message chain "Fixed PHY problems"
for interfacing a fixed PHY to a 83xx UEC. Could you please forward on
the patch you mentioned in the trail?
Vitaly sent me the patch, had to do some minor tweaking to make it
compile. Attaching the patch.
Any ideas if the implementation succeeded in the end?
No, the fixed PHY is on another bus than what ucc_geth expects.
See msg from me titled "Fixed PHY and MPC832x based boards don't work"
from about a week ago.
Jocke
Christian Hammond
NCSG Applications Engineer
Tel: +44 1355 355962
Fax: +44 1355 261790
Freescale Semiconductor
Kelvin Industrial Estate
East Kilbride
Glasgow G75 0TG
United Kingdom
Thanks,
Regarding the PHY set-up in the dts once the patch has been applied, how
should it be implemented?
I had edited from...
phy1: ethernet-phy@01 {
reg =3D <0>;
device_type =3D "ethernet-phy";
interface =3D <6>;
};=20
To...
phy1: fixed-phy@64 {
reg =3D <d#100>;
device_type =3D "ethernet-phy";
interface =3D <6>;
};
When bringing up the fixed phy in ifconfig I get the following recurring
dump and prompt access is lost. Should this implementation not just
ignore the phy set-up?
~ # ifconfig eth1 10.137.32.175 netmask 255.255.255.0 up
read wrong value : mii_id 100,mii_reg 2, base d100c120
read wrong value : mii_id 100,mii_reg 3, base d100c120
eth1: PHY is Generic MII (ffffffff)
~ # read wrong value : mii_id 100,mii_reg 4, base d100c120
read wrong value : mii_id 100,mii_reg 0, base d100c120
read wrong value : mii_id 100,mii_reg 1, base d100c120
read wrong value : mii_id 100,mii_reg 1, base d100c120
read wrong value : mii_id 100,mii_reg 5, base d100c120
eth1: Full Duplex
eth1: Speed 100BT
eth1: Link is up
read wrong value : mii_id 100,mii_reg 1, base d100c120
read wrong value : mii_id 100,mii_reg 1, base d100c120
read wrong value : mii_id 100,mii_reg 5, base d100c120
=20
-----Original Message-----
From: Joakim Tjernlund [mailto:joakim.tjernlund@transmode.se]=20
Sent: 20 May 2007 11:17
To: Hammond Christian-r55079
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Fixed PHY problems
On Sat, 2007-05-19 at 15:42 +0100, Hammond Christian-r55079 wrote:Hi Vitaly,
=20
I was pointed in the direction of message chain "Fixed PHY problems"
for interfacing a fixed PHY to a 83xx UEC. Could you please forward on
the patch you mentioned in the trail?
Vitaly sent me the patch, had to do some minor tweaking to make it
compile. Attaching the patch.
=20
Any ideas if the implementation succeeded in the end?
No, the fixed PHY is on another bus than what ucc_geth expects.
See msg from me titled "Fixed PHY and MPC832x based boards don't work"
from about a week ago.
Jocke
=20
Christian Hammond
=20
NCSG Applications Engineer
=20
Tel: +44 1355 355962
Fax: +44 1355 261790
=20
Freescale Semiconductor
Kelvin Industrial Estate
East Kilbride
Glasgow G75 0TG
United Kingdom
On Mon, 2007-05-21 at 13:46 +0100, Hammond Christian-r55079 wrote:
Thanks,
=20
Regarding the PHY set-up in the dts once the patch has been applied, =
how
should it be implemented?
=20
I had edited from...
=20
phy1: ethernet-phy@01 {
reg =3D <0>;
device_type =3D "ethernet-phy";
interface =3D <6>;
};=20
=20
To...
=20
phy1: fixed-phy@64 {
reg =3D <d#100>;
device_type =3D "ethernet-phy";
interface =3D <6>;
};
=20
When bringing up the fixed phy in ifconfig I get the following =
recurring
dump and prompt access is lost. Should this implementation not just
ignore the phy set-up?
Yes, but some bits are missing and I don't know OF/PHY lib/MDIO well
enough to make out what to do.
Jocke