mostek@laidbak.UUCP (Jim Mostek) (07/26/85)
I'd like to hear from anybody who's written device drivers that
talk to protocol implementations (like TCP/IP) running on front end
processors. I'm also interested in drivers that actually implement
the protocols themselves. In particular:
- How difficult were these drivers to write and debug compared to,
say, a tty device driver?
- How big were they, again compared to something like a tty driver?
- How difficult was the driver implementation compared to doing it
under some other operating system?
- And, finally, how does the complexity of a driver that implements
the protocol compare with one that just talks to a front end
processor running the protocol?
Thanks.
Jim Mostek ihnp4!laidbak!mosteknetworks@dartvax.UUCP (Special Projects Group) (08/01/85)
Please *post* any information you have about this, including pointers
on how to do it, et all. We're just starting in implement our own
Kiewit Stream Protocol under 4.2 BSD and would like to get a good idea
of what we're letting ourselves in for. If you've done it, what sort of
experience did you have before you started, how many people worked on
it, for how long, etc, etc, etc. Many thanks, in advance.
--
David C. Kovar -- Special Projects Group
USNET: {linus|decvax|cornell|astrovax}!dartvax!networks
ARPA: networks%dartmouth@csnet-relay
CSNET: networks@dartmouth
US Mail: Kiewit Computation Center
Dartmouth College
Hanover NH
03755
Phone: (603) 646-3144