[c-nsp] CRC errors on fastethernet interface

[Nick Hilliard]

On 26/11/2012 19:10, Mike Andrews wrote:
> Probably because some (most?) revisions of the Tulip had buggy/broken
> auto-negotiation logic.  

they weren't alone in this, then.

> They're probably the source of most the early
> hardcoding-speed-and-duplex bad practices.  The combo of Tulip to 2924XL
> was particularly awful in my experience and pretty much required hardcoding
> speed/duplex on servers and switches...

The 2924xl had some really atrocious bugs (vlan leakage anyone...?).  I
really don't think you should use this as an example of why other equipment
was broken :-)

> DEC made some nice things in their heyday, but the Tulip chip was
> reeeeeeallly not one of them...

It wasn't that bad in comparison to what was available at the time.  Ok,
it's pretty poor in retrospect, but it's more useful to judge things
according to the standards of the time.

I prefer Gert's explanation that the issue was related to the particular
type of transceiver which the card used.  It sounds more truthy.

Nick