David Greenman 14c77d8a98 After carefully reading three reference documents, and analyzing ... the 802.3 frames generated by the DC21040 (which does automatic padding of less-than-minimum frames) and the frames generated by the 'ed' driver, I've found that there is indeed a bug in the size of "ETHER_MIN_LEN" as reported by several people, John Hay being the most recent. The driver was actually setting the length to 6+6+2+50 (64 bytes), which when adding in the CRC (which is automatically appended to the frame and not included in the length), the minimum frame is 4 bytes larger than it is supposed to be. All of this is confirmed by tcpdump showing 50 bytes of data for minimum frames from the 'ed' cards and 46 bytes from 'de' cards. This analysis has also revealed that there is garbage in the un-filled in portion at the end of the minimum frames from the 'ed' driver; I don't plan to fix this.		1995-05-14 11:01:20 +00:00
..
if_ed.c	After carefully reading three reference documents, and analyzing	1995-05-14 11:01:20 +00:00
if_edreg.h	Much better fix/support for the 83c795 based cards (the new SMC EtherEZ)	1995-01-23 19:06:08 +00:00