ppc405_enet problems

7 messages, 4 authors, 2001-12-11 · open the first message on its own page

ppc405_enet problems

From: Felix Radensky <hidden>
Date: 2001-12-10 13:28:13 

Hi,

I'm trying to run the latest linuxppc_2_4_devel kernel on
our custom 405GP based board. I get kernel panic when an
attempt is made to probe for ethernet controller phy:

Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!

The phy is National Semiconductor DP83846AVHG.
It works fine with Monta Vista HHL 2.0 kernel.

What you think could be the problem ?

TIA.

Felix.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ppc405_enet problems

From: Tom Rini <hidden>
Date: 2001-12-10 16:17:02 

On Mon, Dec 10, 2001 at 03:28:13PM +0200, Felix Radensky wrote:
Hi,

I'm trying to run the latest linuxppc_2_4_devel kernel on
our custom 405GP based board. I get kernel panic when an
attempt is made to probe for ethernet controller phy:

Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!

The phy is National Semiconductor DP83846AVHG.
It works fine with Monta Vista HHL 2.0 kernel.
IIRC, the hhl 2.0 kernel assumes that you have a National Semiconductor
DP83843.  I'm guessing the 83846 is similar enough such that it just
works.  Take a look at drivers/net/ppc405_phy.c, and add in support for
your PHY (and please sumbit a patch to the list).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ppc405_enet problems

From: Felix Radensky <hidden>
Date: 2001-12-10 17:56:18 

Hi,

Support for DP83846A is already present in drivers/net/ppc405_phy.c
My guess is that phy reading fuctions are misbehaving, since i keep
getting different values of Phy id on each boot.

Felix.

Tom Rini wrote:

On Mon, Dec 10, 2001 at 03:28:13PM +0200, Felix Radensky wrote:
quoted
Hi,

I'm trying to run the latest linuxppc_2_4_devel kernel on
our custom 405GP based board. I get kernel panic when an
attempt is made to probe for ethernet controller phy:

Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!

The phy is National Semiconductor DP83846AVHG.
It works fine with Monta Vista HHL 2.0 kernel.
IIRC, the hhl 2.0 kernel assumes that you have a National Semiconductor
DP83843.  I'm guessing the 83846 is similar enough such that it just
works.  Take a look at drivers/net/ppc405_phy.c, and add in support for
your PHY (and please sumbit a patch to the list).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ppc405_enet problems

From: Armin Kuster <hidden>
Date: 2001-12-10 20:03:34 

Felix Radensky wrote:
Hi,

Support for DP83846A is already present in drivers/net/ppc405_phy.c
My guess is that phy reading fuctions are misbehaving, since i keep
getting different values of Phy id on each boot.

Felix.
Felix,

 try increasing in the "udelay(10)" in the  fec_enet_mdio_read

--armin

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ppc405_enet problems

From: David Müller (ELSOFT AG) <hidden>
Date: 2001-12-11 07:51:33 

It looks like the MII controller is not setting the error flag for the
first access (reading of PHYIR1 in find_phy(ppc405_phy.c)

Perhaps my work-around (see attached file) will help you too.


Felix Radensky wrote:

 > Hi,
 >
 > I'm trying to run the latest linuxppc_2_4_devel kernel on
 > our custom 405GP based board. I get kernel panic when an
 > attempt is made to probe for ethernet controller phy:
 >
 > Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!
 >
 > The phy is National Semiconductor DP83846AVHG.
 > It works fine with Monta Vista HHL 2.0 kernel.
 >
 > What you think could be the problem ?
 >
 > TIA.
 >
 > Felix.
 >


Dave

Re: ppc405_enet problems

From: Felix Radensky <hidden>
Date: 2001-12-11 13:32:52 

Hi,

Thanks, David and Armin for your help. I've tried the methods you suggested
but none of them worked. The real problem in my case was the MAX_NUM_PHYS
constant. I've noticed that after the first for loop in find_phy routine, the
value of
i is MAX_NUM_PHYS. So I've tried to increase the value of this constant, and
my
phy was (almost) discovered properly after the 5th iteration. I say almost,
because
I also had to change the value of phy id from 0x20005c23 to 0x20005c20 (the
value
reported by find_phy. Armin, can you please explain how this number was
determined.

After applying the above changes I was able to boot and mount root via NFS.

Another thing I've noticed is that you now have to explicitly specify the ip
address
of NFS server as kernel parameter. The former default (NFS sever = BOOTP
server)
seems not to work anymore.

Felix.


"David Müller (ELSOFT AG)" wrote:
quoted hunk
It looks like the MII controller is not setting the error flag for the
first access (reading of PHYIR1 in find_phy(ppc405_phy.c)

Perhaps my work-around (see attached file) will help you too.

Felix Radensky wrote:

 > Hi,
 >
 > I'm trying to run the latest linuxppc_2_4_devel kernel on
 > our custom 405GP based board. I get kernel panic when an
 > attempt is made to probe for ethernet controller phy:
 >
 > Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!
 >
 > The phy is National Semiconductor DP83846AVHG.
 > It works fine with Monta Vista HHL 2.0 kernel.
 >
 > What you think could be the problem ?
 >
 > TIA.
 >
 > Felix.
 >

Dave

  ------------------------------------------------------------------------
--- 1.5/drivers/net/ppc405_phy.c        Thu Oct 25 00:44:15 2001
+++ edited/ppc405_phy.c Mon Dec  3 16:51:05 2001
@@ -707,14 +707,17 @@
 {
        struct fec_enet_private *fep;
        int i;
-       uint phy_reg;
+       uint phy_reg, phy_reg2;
        uint phytype;

        fep = dev->priv;

        for ( i = 0; i < MAX_NUM_PHYS; i++)
-               if (!(fec_enet_mdio_read(i, mk_mii_read(MII_REG_PHYIR1),
-                                               &phy_reg)))
+               if (!((fec_enet_mdio_read(i, mk_mii_read(MII_REG_PHYIR1),
+                                               &phy_reg)) ||
+                     (fec_enet_mdio_read(i, mk_mii_read(MII_REG_PHYIR2),
+                                               &phy_reg2))))
+
                        break;

        fep->phy_addr = i;

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ppc405_enet problems

From: Armin Kuster <hidden>
Date: 2001-12-11 18:11:28 

Felix Radensky wrote:
Hi,

Thanks, David and Armin for your help. I've tried the methods you suggested
but none of them worked. The real problem in my case was the MAX_NUM_PHYS
constant. I've noticed that after the first for loop in find_phy routine, the
value of
i is MAX_NUM_PHYS. So I've tried to increase the value of this constant, and
my
phy was (almost) discovered properly after the 5th iteration. I say almost,
because
I also had to change the value of phy id from 0x20005c23 to 0x20005c20 (the
value
reported by find_phy. Armin, can you please explain how this number was
determined.
Felix,

I took the easy route, its just phyid1 & phyid2.  The "A" version was
submitted by some one else and it might be possible to combine them into
one DP83843 stuct by using a shift factor of 8 ( 2nd eliment in the
phy_info struct" the diff between 0x20005c23 &  0x20005c20 is the model
revision number.

Maybe MAX_NUM_PHYS needs to be renamed to MAX_PHY_ADDR to be more clear.


-- armin

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help