home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!waikato.ac.nz!comp.vuw.ac.nz!gnat
- Newsgroups: comp.os.linux
- Subject: Re: Ethernet drivers
- Message-ID: <GNAT.92Sep1191408@kauri.kauri.vuw.ac.nz>
- From: gnat@kauri.vuw.ac.nz (Nathan Torkington)
- Date: Tue, 1 Sep 1992 07:14:08 GMT
- Sender: news@comp.vuw.ac.nz (News Admin)
- References: <1992Aug28.114807.7765@athena.mit.edu> <#xdngk+@quantum.on.ca>
- Organization: Contract to CSC, Victoria Uni, Wellington, New Zealand
- Nntp-Posting-Host: kauri.vuw.ac.nz
- In-Reply-To: aboyd@quantum.on.ca's message of Fri, 28 Aug 92 17:31:34 GMT
- Lines: 18
-
- In article <#xdngk+@quantum.on.ca> aboyd@quantum.on.ca (Andrew Boyd) writes:
-
- > Actually, the 503 is very similar to the wd (now smc) 8003 series of
- > cards - both use the 8390 NIC. If you folks already have a driver for
- > the 8003, you won't find it too big a job to support the 503 - just
- > different locate and init code. The runtime code is identical.
-
- Can I take this to mean that because the (almost undocumented) crynwr
- source for the ne1000 MS-DOS packet driver does an include of
- 8390.inc, that implies that the ne1000 is also similar to the 8003?
- If I can, then does this mean that "making" an ne1000 driver would be
- similarly "simple"?
-
- Nat (I tell ya, trying to work out the differences between the ne1000
- and 8003e MS-DOS packet drivers, and the similarities between the
- 8003e MS-DOS packet driver and the 80[01]3 Linux device driver, and
- then trying to change the Linux device driver to work with an ne1000
- is *not* easy!)
-