-----Original Message-----
From: <redacted> [mailto:<redacted>]
On Behalf Of Andrew Lunn
Sent: Tuesday, January 16, 2018 5:04 PM
To: mad skateman <redacted>
Cc: Christian Zigotzky <redacted>; Joakim Tjernlund
[off-list ref]; linuxppc-dev@lists.ozlabs.org; Madalin-
cristian Bucur [off-list ref]; netdev@vger.kernel.org
Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
quoted
When i use mii-tool too Kick the tranceiver... it comes alive.. i can
ping the eth0 itself
root@X5000LNX:/home/skateman# mii-tool -R eth0
resetting the transceiver...
root@X5000LNX:/home/skateman# ping 192.168.22.44
PING 192.168.22.44 (192.168.22.44) 56(84) bytes of data.
64 bytes from 192.168.22.44: icmp_seq=1 ttl=64 time=0.045 ms
64 bytes from 192.168.22.44: icmp_seq=2 ttl=64 time=0.046 ms
64 bytes from 192.168.22.44: icmp_seq=3 ttl=64 time=0.047 ms
64 bytes from 192.168.22.44: icmp_seq=4 ttl=64 time=0.048 ms
What PHY driver are you using?
This smells a bit like an RGMII-ID problem.
Andrew
Hi Andrew,
From another thread[1] on the same topic:
I am not sure what PHY hardware/configuration you are using on the
DS and RDB platforms, but I can confirm that AmigaONE X5000/20
(Cyrus Motherboard with p5020 SoC), has dTSEC 4 and dTSEC 5
wired to two Micrel KSZ9021RN Gigabit Ethernet PHYs, using the
RGMII protocol.
[1] https://www.spinics.net/lists/netdev/msg478062.html