<div>As part of the port of our device (MPC8271 based) from 2.6.23 using arch/ppc to 2.6.24 arch/powerpc, I've hit a road block in the past few days in trying to make FS_ENET (freescale)/CPM2 recognize the BCM5221 PHY, which means I can't get eth0 up and running.</div> <div>It worked fine in 2.26.23 arch/ppc when configured as FEC_ENET.</div> <div> </div> <div>As far as I can tell, the "dts" is fine for FCC2 (see below), with the proper pins connected to the device/phy:</div> <div> <A href="mailto:mdio@10d60">mdio@10d60</A> {<BR> device_type =
"mdio";<BR> compatible = "fsl,mpc8272ads-mdio-bitbang",<BR> "fsl,mpc8272-mdio-bitbang",<BR>
"fsl,cpm2-mdio-bitbang";<BR> reg = <10d60 14>;<BR> #address-cells = <1>;<BR> #size-cells = <0>;<BR> fsl,mdio-pin = <1d>;
<BR> fsl,mdc-pin = <17>;</div> <div> PHY0: <A href="mailto:ethernet-phy@0">ethernet-phy@0</A> {<BR> interrupt-parent = <&PIC>;<BR>
interrupts = <31 8>;<BR> reg = <4>;<BR> device_type = "ethernet-phy";<BR> };</div> <div> };</div>
<div> <A href="mailto:ethernet@11320">ethernet@11320</A> {<BR> device_type = "network";<BR> compatible = "fsl,mpc8272-fcc-enet",<BR>
"fsl,cpm2-fcc-enet";<BR> reg = <11320 20 8500 100 113b0 1>;<BR> local-mac-address = [ 00 00 00 00 00 00 ];<BR> interrupts = <21 8>;<BR> interrupt-parent =
<&PIC>;<BR> phy-handle = <&PHY0>;<BR> linux,network-index = <0>;<BR> fsl,cpm-command = <16200300>;<BR> };<BR></div> <div> </div> <div>During my debugging, it appears to be that the PHY is not detected during </div> <div>drivers/net/phy/phy_device.c:
get_phy_device(..)</div> <div>Basically, the phy_id is 0xFFFFFFFF.</div> <div> </div> <div>I'm going to try to put a probe on the MDIO/MDC lines later on, but I was wondering whether anyone would have any ideas as to what could be wrong.</div> <div> </div> <div>thanks</div> <div> </div><p> 
<hr size=1>
Looking for the perfect gift?<a href="http://www.flickr.com/gift/"><b> Give the gift of Flickr!</b></a>