Thread (8 messages) 8 messages, 3 authors, 2009-03-04

Re: How to bring up fs_enet on 2.6.27?

From: Daniel Ng <hidden>
Date: 2009-02-25 07:09:34

Possibly related (same subject, not in this thread)

Hi guys,

I was hoping to have gotten some form of comment by now...

Can anyone help out here, please?

Daniel

On Fri, Feb 20, 2009 at 4:01 PM, Daniel Ng [off-list ref] wrote:
Now, I'm seeing these boot messages:

f0010d40:00 not found
eth0: Could not attach to PHY
IP-Config: Failed to open eth0
IP-Config: Device `eth0' not found.

Previous mailing list discussions suggest that I use the correct PHY,
which I am sure about because my 8272-based board only has the one PHY
ie. PHY0 with reg =3D <0x0>.

Note the relevant parts of my Device Tree below. Currently, our PHY
attributes eg. 'auto-negotiate' are not changeable, so we aren't
actually using MDC+MDIO even the MDC+MDIO lines exist. Also, the PHY
interrupt line is not wired up. Hence the PHY0 interrupts field is <0
8> (or should it be removed altogether?).

I am usig FCC2.

What might I need to change to get the ethernet driver working?


=A0 =A0 =A0ethernet@11320 {
=A0 =A0 =A0 =A0device_type =3D "network";
=A0 =A0 =A0 =A0compatible =3D "fsl,mpc8272-fcc-enet",
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 "fsl,cpm2-fcc-enet";
=A0 =A0 =A0 =A0// FCC2-
=A0 =A0 =A0 =A0reg =3D <0x11320 0x20 0x8500 0x100 0x113b0 0x1>;
=A0 =A0 =A0 =A0local-mac-address =3D [ 00 00 00 00 00 00 ];
=A0 =A0 =A0 =A0interrupts =3D <33 8>;
=A0 =A0 =A0 =A0interrupt-parent =3D <&PIC>;
=A0 =A0 =A0 =A0phy-handle =3D <&PHY0>;
=A0 =A0 =A0 =A0linux,network-index =3D <0>;
=A0 =A0 =A0 =A0fsl,cpm-command =3D <0x16200300>;
=A0 =A0 =A0};

=A0 =A0 =A0mdio@10d40 {
=A0 =A0 =A0 =A0device_type =3D "mdio";
=A0 =A0 =A0 =A0compatible =3D "fsl,mpc8272ads-mdio-bitbang",
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 "fsl,mpc8272-mdio-bitbang",
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 "fsl,cpm2-mdio-bitbang";
=A0 =A0 =A0 =A0reg =3D <0x10d40 0x14>;
=A0 =A0 =A0 =A0#address-cells =3D <1>;
=A0 =A0 =A0 =A0#size-cells =3D <0>;
=A0 =A0 =A0 =A0fsl,mdio-pin =3D <5>;
=A0 =A0 =A0 =A0fsl,mdc-pin =3D <19>;

=A0 =A0 =A0 =A0PHY0: ethernet-phy@0 {
=A0 =A0 =A0 =A0 =A0interrupt-parenn =3D <&PIC>;
=A0 =A0 =A0 =A0 =A0interrupts =3D <0 8>;
=A0 =A0 =A0 =A0 =A0reg =3D <0x0>;
=A0 =A0 =A0 =A0 =A0device_type =3D "ethernet-phy";
=A0 =A0 =A0 =A0};
.
.
.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0PIC: interrupt-controller@10c00 {
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0#interrupt-cells =3D <2>;
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0interrupt-controller;
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D <0x10c00 0x80>;
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0compatible =3D "fsl,mpc827=
2-pic", "fsl,cpm2-pic";
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};

Cheers,
Daniel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help