Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: [TU81 drivers] UNIX-WIZARDS Digest  V2#062
Message-ID: <2996@umcp-cs.UUCP>
Date: Sat, 1-Feb-86 21:51:02 EST
Article-I.D.: umcp-cs.2996
Posted: Sat Feb  1 21:51:02 1986
Date-Received: Mon, 3-Feb-86 05:38:32 EST
References: <2128@brl-tgr.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 24

In article <2128@brl-tgr.ARPA> MRC%PANDA@sumex-aim.arpa writes:
> I don't see what is so hard about writing a device driver for the
> TU81.  Tape drives are tape drives.

You obviously have not seen MSCP yet.  Tape drives are disks connected
via a virtual circuit network :-).

> A good hacker should be able to knock off a nerdly tape drive device
> driver in a day or so, and a good (fully compatible) one in a week
> at most.

*If* you have manuals.  Without knowing which device registers to
poke, with which values, and without circuit diagrams and microcode
listings and all, it can take a LONG time to figure out how ANYTHING
works.

Speaking of which . . . does anyone have an order number for a TU81
programmer's manual?  As long as I am rewriting the UDA50 driver
I would like to write some generic MSCP device routines; it would
help if I knew which MSCP things were truly generic.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu