<mtrbot-ml>
[mattermost] <sb10q> in fact this is exactly what is happening right now, with the current code implementing AN but with only one protocol advertised
kuldeep has quit [Quit: Its never too late!]
kuldeep has joined #m-labs
proteusguy has quit [Ping timeout: 256 seconds]
proteus-guy has quit [Ping timeout: 258 seconds]
proteus-guy has joined #m-labs
proteusguy has joined #m-labs
_whitelogger has joined #m-labs
_whitelogger has joined #m-labs
_whitelogger has joined #m-labs
X-Scale` has joined #m-labs
X-Scale has quit [Ping timeout: 264 seconds]
X-Scale has joined #m-labs
X-Scale` has quit [Ping timeout: 272 seconds]
vaishali has quit [Quit: Connection closed for inactivity]
<mtrbot-ml>
[mattermost] <dpn> rjo: Oh, sure, I couldn't care less about whether not supporting 10/100 is compliant with the spec – just pointing out that since GbE it has become so uncommon for things not to just auto-negotiate their way to a working connection that the potential for ports to mismatch has pretty much left the collective understanding of how Ethernet works
craigo has joined #m-labs
<rjo>
In this case it's down to supporting 10/100 (maybe also half duplex).
Stormwind_mobile has quit [Ping timeout: 256 seconds]