On Wed, Feb 25, 2009 at 06:09:32PM +1100, Daniel Ng wrote: > On Fri, Feb 20, 2009 at 4:01 PM, Daniel Ng <daniel.ng1...@gmail.com> 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 = <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.
Your device tree is telling the kernel that you *are* using those lines. If they're not connected the way the device tree describes them as being connected, you'll have to replace it with something that accurately describes your hardware. > > Also, the PHY interrupt line is not wired up. Hence the PHY0 interrupts > > field is <0 8> (or should it be removed altogether?). If your PHY interrupt is not connected, then you must remove the "interrupts" property altogether. "0" is a potentially valid interrupt number. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
