Gerald said: The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine.
Could we get a clue about which "addresses" are the problem? Maybe the addresses 4a100000 vs. 4a101000? davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00 --- cpsw 4a100000.ethernet: Or maybe the mask that seems to select the particular phy? davinci_mdio 4a101000.mdio: detected phy mask fffffffb --- davinci_mdio 4a101000.mdio: detected phy mask fffffffe Or the "phy id" which I haven't a clue about? net eth0: phy found : id is : 0x7c0f1 Or maybe the default MAC addresses, two in the onboard hardware memory and more in the boot environment? I still see lots of "phy not found" dmessages, even though all of my interfaces work properly when connected. Would be nice to understand this better... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
