On 06.06.19 15:35, Andrew Lunn wrote: >> >From our hardware developer I know now that we are using a "mini" SFF >> which has no i2c eeprom. > O.K. Does this mini SFF have LOS, TX-Disable, etc? Are these connected > to GPIOs? I assume the SFF is fibre? And it needs the SERDES to speak > 1000BaseX, not SGMII?
Nope, no LOS no tx-disable etc. Yeah, the SFF is fibre. Exactly, it needs SERDES to speak 1000BaseX. > >> Switch | external >> Port 0 - internal serdes 0x0c --|-------Mini SFF 1x8 Transceiver >> | >> Port 0 - internal serdes 0x0d --|-------Mini SFF 1x8 Transceiver >> | >> Port 2 ----------RGMII----------|-------KSZ9031 PHY 0x02(strap)--Transceiver >> | >> Port 3 - internal PHY 0x03 -----|-------Transceiver >> | >> Port 3 - internal PHY 0x04 -----|-------Transceiver >> | >> Port 5 - CPU-Port RMII ---------|-------CPU >> | >> Port 6 ----------RGMII----------|-------KSZ9031 PHY 0x06(strap)--Transceiver > So the current state is that just the SFF ports are not working? All > the copper PHYs are O.K. > > Andrew > The external copper PHYs are still not working properly, but if I set them to fixed-link, I see data coming in with I start tcpdump on my device. Just with some odd header but I'm not that far with DSA-tags and these stuff. Just at that moment we found out that we have a problem with our MDC timing. After we fixed that the external PHY registers could be read correctly over SMI Command registers. But I haven't tested it with the DSA driver yet.
