PPC4xx enet driver problem (version 2.0)

Matt Porter mporter at kernel.crashing.org
Sat Dec 13 01:45:41 EST 2003

On Fri, Dec 12, 2003 at 11:56:09AM +0100, Stefan Roese wrote:
> Davey!
> No, we didn't solve this problem so far. Eugene did some tests on an
> ppc440 board and had no problems with the multiple enet devices. So it
> seems to be 405ep related! I still have to send some debug output to
> Eugene (hopefully today)!

[I haven't followed the thread but new EMAC driver and 405EP rings
 a bell]

It's possible that the new method in which OCP code handles OCP device
dependencies has a bug.  405ep is a special case since it requires
a particular EMAC device to provide MDIO operations for both EMACs.
440gp/gx don't follow this code path.


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

More information about the Linuxppc-embedded mailing list