Re: tulip not correctly identifying LNE100TX
Dave Platt <[email protected]> Tue, 9 Jul 2002 12:34:41 -0700 (PDT)
| Newsgroups | gmane.linux.drivers.tulip.bugs |
|---|---|
| Message-ID | <[email protected]> |
> The ADMtek Centaur is an all-in-one chip. There is no way for a board > designer to screw it up, so there no reason to identify the specific > board. #laughing out loud# I recall one of the very first boards I bought which had an AMD PCNet-PCI chip on it. The manufacturer (Boca) had ignored Appendix B in the data sheet, and had installed less than half of the ceramic-chip and tantalum bypass caps which AMD said were essential for reliable operation. The board worked fine, up until the moment when a particular data pattern caused the chip's analog inputs to suffer from enough ground-bounce and Vcc ringing to drop bits. The chip would detect an FCS mismatch and drop the packet, the sending system would time out and resend it, the re-sent packet would hit the same error, etc. It was quite maddening... FTP connections would freeze up, while a TELNET session to the same host worked fine. Granted, this isn't a screwup which would require (or be helped by) any sort of software configuration fix, but it did teach me a valuable lesson: there's no design so foolproof that an idiot board designer can't make a mess of it. [Naturally, an analogous situation exists in software design!] _______________________________________________ tulip-bug mailing list, [email protected] To change to digest mode or unsubscribe visit http://www.scyld.com/mailman/listinfo/tulip-bug