Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!utah-cs!cetron
From: cetron@utah-cs.UUCP (Edward J Cetron)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.org.usenix
Subject: Re: dr11w driver
Message-ID: <4187@utah-cs.UUCP>
Date: Tue, 20-Jan-87 12:21:58 EST
Article-I.D.: utah-cs.4187
Posted: Tue Jan 20 12:21:58 1987
Date-Received: Wed, 21-Jan-87 00:36:03 EST
References: <6429@allegra.UUCP> <5127@mimsy.UUCP>
Reply-To: cetron@utah-cs.UUCP (Edward J Cetron)
Organization: Center for Engineering Design, Univ of Utah
Lines: 26
Xref: mnetor comp.unix.questions:765 comp.unix.wizards:656 comp.org.usenix:30

In article <5127@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
->>If anyone has or knows of a dr11w device driver which runs under
->>Berkeley Unix version 4.3, PLEASE send me Email. ...
->
->Why is it that as soon as it is explained why this is an unreasonable
->or incomplete request, six of them appear?  The DR11W does not *do*
->anything by itself.  One can ask for a driver for `a DR11W connected
->to a Foomix Graphi-Phaser II' or `a DR11W connected to a Blorch Inc.
->Bus Buster' or whatever, but asking for a DR11W driver is somewhat
->like asking for a Unibus Adapter driver.

	I disagree, a dr11w is going to use the same general interface
REGARDLESS of what is on the other end.  You still need to set up the
same data structures, poke it the same way, and read it the same way.
Granted that there will be major philosophy differences depending on what
it will talk to, but I'd rather have a working driver for the right board
which is CLOSE, then start from scratch......  I think that the hardest 
part of writing a driver is the device interface and its structures and the
kernel interface and its structures.... the flow of the code is easy by
comparison.....

-ed cetron
center for engineering design
univ of utah
cetron%utah-ced@utah-cs.arpa
cetron@utahcca.bitnet