On Fri, Jul 28, 2017 at 1:03 AM, Nerijus Baliunas <neri...@users.sourceforge.net> wrote: > On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov <ryazanov....@gmail.com> > wrote: > >> >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel >> >> messages log? If not then the mwswitch driver did not attached and >> >> you should fix this first. And only then go to the interface >> >> configuration. >> > >> > No, dmesg|grep 6060 does not show anything. How do I fix it? >> >> Try to check, which MDIO addresses PHY core (or Ethernet MAC driver) >> scans to detect connected PHYs. > > I enabled #define DEBUG_MDIO 1 in ixp4xx_eth.c and got this: > # dmesg|grep -i MII|grep -v took > ... > [ 0.976646] IXP4xx MII Bus #16: MII read [2] -> 0x141 > [ 0.976747] IXP4xx MII Bus #16: MII read [3] -> 0xC87 > [ 0.978682] IXP4xx MII Bus #24: MII read [3] -> 0x602
Looks like mvswitch driver tries to check chip here and got an expected value 0x060X from register 3. So on the one hand the driver is functioning, but on the other hand it can not detect switch IC. Can you go to the /sys/class/mdio_bus/ and for each bus check driver and ID of the each detected device. E.g.: # cd /sys/class/mdio_bus # ls -l */*/driver # ls -l */*/phy_id # cat */*/phy_id -- Sergey _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
