home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!sunic!psinntp!psinntp!crynwr!nelson
- From: nelson@crynwr.com (Russell Nelson)
- Newsgroups: comp.os.linux
- Subject: Ethernet drivers
- Distribution: world
- Message-ID: <715399538snx@crynwr.com>
- References: <GNAT.92Sep1191408@kauri.kauri.vuw.ac.nz>
- Date: Wed, 02 Sep 92 02:05:38 GMT
- Organization: Crynwr Software
- Lines: 26
-
- In article <GNAT.92Sep1191408@kauri.kauri.vuw.ac.nz> gnat@kauri.vuw.ac.nz writes:
-
- 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.
-
- Well, that was WRONG. First of all, WD has their own silicon, which
- has different bugs than the National silicon. Plus, the 3c503 when
- I/O mapped has a 16 byte FIFO that you need to ensure is filled.
- Plus, the wd8013e has a 16-bit interface that decodes its address
- early and so needs to be read/written to with interrupts off. The
- 3c503 is an 8-bit board, and the 16-bit version of it doesn't decode
- its address early.
-
- 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"?
-
- Right, it's not as simple as it seems. However, as you've noticed
- from the use of 8390.{inc,asm}, a lot of code can be shared.
-
- -russ <nelson@crynwr.com> I'm proud to be a humble Quaker!
- Crynwr Software Crynwr Software sells packet driver support.
- 11 Grant St. 315-268-1925 Voice
- Potsdam, NY 13676 315-268-9201 FAX
-