On Fri, Dec 23, 2016 at 6:15 PM, Robert Nelson <[email protected]> wrote:
> > the cpsw/eth0 is just broken. ;) i saw on github (irc zmatt) was looking > at it While I don't exclude the possibility that the cpsw driver might be crappy (haven't really looked at it much), the blame here actually lies with linux itself, which unconditionally resets the phy. Latest version of the patch: https://github.com/dutchanddutch/bb-kernel/blob/am33x-v4.9/patches/local/0003-WiP-trying-to-achieve-fast-link-up-at-boot.patch On Saturday, 24 December 2016 02:27:13 UTC+1, William Hermans wrote: > > > hmmm, I wonder if that works ? > If you had Cc'd me then you wouldn't have needed to wonder :-) I'm not going to pretend it's an elegant patch, but we've been using it for months now on all our beaglebones and it appears to work like a charm: [ 5.548658] alexje kernel: net eth0: initializing cpsw version 1.12 (0) [ 5.551254] alexje kernel: SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1) [ 5.551903] alexje kernel: cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 5.593833] alexje systemd-networkd[105]: eth0: Gained carrier Matthijs -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b5407bf8-61d4-4d75-b06b-92d10bc015ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
