On Sun, Feb 24, 2019 at 12:42:35AM +0100, Andrew Lunn wrote: > Looking forward, at some point we are going to have to make fixed-link > support higher speeds. That probably means we need a swphy-c45 which > emulates the standard registers for 2.5G, 5G and 10G. At that point > genphy will not work...
Do we _need_ to emulate Clause 45 PHYs? Today, the MII interface does not work with Clause 45 PHYs, so there is no userspace accessing these PHYs out there. I have a patch that adds support for the MII ioctls which gives me the ability to poke around in the 88x3310 for investigatory / debug purposes. However, I don't see the point of adding what would be very complex Clause 45 support (we'd have to emulate the PMA/PMD, PCS and AN as a minimum) when we have the ethtool API, and then we have the issue that not all advertisement modes are standardised in Clause 45 - there are some missing. As I understand it, the swphy for fixed-links only exists because we have existing tooling that expects Clause 22 PHYs to exist. This will break even if we were to add Clause 45 support as many bits in the first 16 registers have different meanings. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
