Hi Luke.
> I've finally started work on ELKS TCP/IP.
> So far I've been making an ne2000 driver, but I've got some
> books and stuff and I think its do-able.
> Does anyone want to help?
I'd be interested, and I have the pleasure of being a reasonably
experienced C programmer as well. As a result, I'll start by
mentioning a few points relating to various messages in this
thread...
1. You refer to an "NE2000" card. Presumably you're aware that those
normally don't work in an XT as they require an AT style connector
and the similar NE1000 card with its XT style connector has to be
used instead. I'm not sure that the code for one will always work
with the other.
2. Several people refer to reading from the ROM to positively ID the
card. My network consists entirely of NE1000 and NE2000 cards,
none of which have any ROM on board, and all are working fine. As
a result, I would consider ANY code that relies on the contents of
those non-existant ROMs to be highly suspect.
I'll also add that in my opinion, decent TCP/IP support and a working
lpd daemon are all that's required to allow XT's and 286's to be used
under ELKS as network print servers, and that would probably be the
first marketable application for ELKS...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
