On Thursday 23 July 2009 08:16:47 Prafulla Wadaskar wrote:
I'm working on the repo right now and should have another pull request soon. The 'forced interface' patch is still contentious, so isn't included.
Okay With this for RD6281 Build will not fail, but network will be broken. Meanwhile I will check why auto negotiation doesn't work on this board?
Did you check if Lennert's comments are correct?
Quote:
Isn't it just because on the RD6281A, the first ethernet MAC of the CPU is connected to an ethernet switch chip instead of an ethernet PHY, and therefore there is no negotiation to be done? (The second MAC is connected to a PHY directly, so that one should just use autoneg.)
Even on the RD6281Z, we should just force the ethernet MAC to a fixed speed/duplex, since even though PHY polling might work there, we'll be talking to the PHY corresponding to the first switch port, which means that you might not be able to tftp from the second switch port or so if there's nothing plugged into the first one.
FWIW, the linux kernel port also forces 1000/full on the CPU MACs where a switch chip is connected. On those CPU MACs where there is a switch chip connected, the (R)(G)MII interface becomes purely a bus to transport packets into and out of the crossbar, one that is always up.
So, is this ethernet port in question connected to switch? Then a forced link (highest speed) should be used.
Best regards, Stefan
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de =====================================================================