Hi Jonathan.
>> We're gonna need a tcp/ip stack first. A plip driver won't be that
>> hard, but we need something for it to sit on.
> The problem with PLIP in ELKS will be finding XTs with
> bi-directional parallel ports.
Whilst PLIP will make good use of bidirectional parallel ports, it
doesn't need them as it can use the so-called LapLink protocol that
turns a unidirectional parallel port into a bidirectional 4-bit port.
Memory says it makes use of five of the status lines as inputs that
are connected to five of the data lines at the other end, and that
gives four data lines and a strobe signal each way.
> And finding 8-bit parallel add-on cards that support
> bi-directional transfers.
Given a 286 based system, the 16-bit EPP cards that are common in the
local emporiums round here can easily be used, so that's unlikely to
be a headache...
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
