On Wed, Jun 19, 2024 at 09:29:03PM +0200, Bartosz Golaszewski wrote: > On Wed, Jun 19, 2024 at 9:09 PM Andrew Lunn <andrew@xxxxxxx> wrote: > > > > On Wed, Jun 19, 2024 at 08:45:42PM +0200, Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > > > > > The Aquantia AQR115C PHY supports the Overlocked SGMII mode. In order to > > > support it in the driver, extend the PHY core with the new mode bits and > > > pieces. > > > > Here we go again.... > > > > Admittedly I don't post to net very often and I assume there's a story > to this comment? Care to elaborate? 2.5G is a mess because vendors implemented it before the standard came out, in the form of 2500BaseX. They often did just what this seems to suggest, they overclocked CISCO SGMII. But the in-band signalling SGMII uses cannot work at 2.5G, it makes no sense. So vendors disable the in-band signalling. What you likely end up with, is 2500BaseX, but without in-band signalling. Now, some real 2500BaseX devices require the peer to perform in-band signalling. Some will listen for the signalling a while, and if they hear nothing will go into some sort of fallback mode. Others can be told the peer does not support inband signalling, and so don't expect it. And then we have those which are overclocked SGMII which don't expect any signalling because SGMII signalling makes no sense at 2.5G. phylib supports out of band signalling, which is enough to make this work, so long as two peers will actually establish a link because they are sufficiently tolerant of what the other end is doing. Sometimes they need a hint. Russell King has been working on this mess, and i'm sure he will be along soon. What i expect will happen is you keep calling this 2500BaseX, without in band signalling. You can look back in the netdev mailling list for more details and those that have been here before you. It is always good to search the history, otherwise you are just going to repeat it. Andrew
