My MDIO is acting strange

My MDIO is acting strange

[Peter Pan]

I'm porting Linux 2.6.32.6 to my MPC8247 based board. Our FCC1 and
FCC2 are used as 100MBps ethernet ports. MDIO is used to connect with
PHY chip. During boot, the of driver is checking the PHYID, it gets
all Fs. But after I comment the following lines:
//if ((phy_id & 0x1fffffff) == 0x1fffffff)
//    return NULL;
I can use my FCC ethernet normally after boot into console.
I checked that while boot, all the read bit from MDIO pin is 1, that
makes no TA bit, and no PHYID.
I'm wondering why is that happening.

Re: My MDIO is acting strange

[Peter Pan]

linux 2.6.22 is working correctly on my board. So, I think this is due
to the difference between them.
I will check the boot time difference between 2.6.22 and my new port.
Hope that will give me a clue.

2010/4/23 Andy Fleming <afleming@gmail.com>:
> On Thu, Apr 22, 2010 at 9:36 PM, Peter Pan <pppeterpppan@gmail.com> wrote=
:
>> I'm porting Linux 2.6.32.6 to my MPC8247 based board. Our FCC1 and
>> FCC2 are used as 100MBps ethernet ports. MDIO is used to connect with
>> PHY chip. During boot, the of driver is checking the PHYID, it gets
>> all Fs. But after I comment the following lines:
>> //if ((phy_id & 0x1fffffff) =3D=3D 0x1fffffff)
>> // =A0 =A0return NULL;
>> I can use my FCC ethernet normally after boot into console.
>
> This means that your PHY can work without any initialization, and
> implies the problem is with your MDIO bus.
>
>> I checked that while boot, all the read bit from MDIO pin is 1, that
>> makes no TA bit, and no PHYID.
>> I'm wondering why is that happening.
>
> Possible reasons include the board being wired incorrectly (so the PHY
> is not responding to MDIO commands), or software being configured
> incorrectly to use the wrong pins for MDIO. =A0That's my guess.
>
> Andy
>