Date: Thu, 9 Jul 1998 09:56:36 -0400 From: sbabkin@dcn.att.com To: mike@smith.net.au Cc: hackers@FreeBSD.ORG Subject: RE: NIC drivers Message-ID: <C50B6FBA632FD111AF0F0000C0AD71EEFF8B5A@dcn71.dcn.att.com>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > > > >> Just curious, how do one find the neccesary info to write a > driver of > > >> say 3c509 fro FreeBSD? > > > You mean like, eg. /sys/i386/isa/if_ep.c? (The 3c509 driver.) > > > > Last I heard, the 509 driver was buggy. (According to LINT, it > still > > is.) When I last tried it about eight months ago, it was still > buggy. > > Cursory tests now (I've got one in this box, on the same LAN as an > > NE2000) indicate that it may still be broken. > > Yes; the driver is not spectacular, and neither is the card. > It worked fine for me in '95-'97 in my machine at work. Yes, it occasionally loses packets under high load but it's still faster than NE2000 (although I agree that the card is somewhat pathological). It can easily handle FTP at full Ethernet speed (1.1MB/s) in an old 486. Although I don't know about the current state of the driver. There was a period (early '95) when packet loss led to the hang of the card and that's the reason why it was marked as "buggy" in LINT at that time. This was fixed but this comment just was not cleaned up. There was the same problem somewhere in '96 when David Greenman had changed the way the watchdog routines are called for network drivers, but after this driver was changed according to the new way it worked again. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C50B6FBA632FD111AF0F0000C0AD71EEFF8B5A>