Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!brl-adm!umd5!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu.UUCP
Newsgroups: comp.sys.amiga
Subject: SCSI device drivers
Message-ID: <1548@umd5.umd.edu>
Date: Thu, 16-Apr-87 17:06:29 EST
Article-I.D.: umd5.1548
Posted: Thu Apr 16 17:06:29 1987
Date-Received: Sat, 18-Apr-87 00:00:57 EST
Sender: nobody@umd5.umd.edu
Reply-To: louie@sayshell.umd.edu (Louis A. Mamakos)
Distribution: na
Organization: University of Maryland, College Park
Lines: 24
Summary: Is there a standard interface to SCSI drivers/controllers?

References:

There seems to be more and more SCSI compatible disk systems being released
of late.  One of the wonderfull things about SCSI systems is that you can
hang multiple controllers on the SCSI bus.  Things like disk controllers,
tape controllers, ethernet controllers, etc.

The question is:  just how useful is a vendors SCSI controller if he doesn't
document a software interface to the SCSI host adaptor.  Hopefully, there are
two seperate drivers for such products; the driver to talk to the SCSI host
adaptor and a higher level disk device driver that call upon the SCSI driver
to talk to the SCSI bus.

It there a standard for the interface to the SCSI driver?  Now that Commodore
is jumping into the arena with their SCSI/disk product, maybe they can provide
guidence in this area.  Maybe ASDG has some ideas?

The usefullness of the SCSI bus is pretty much eliminated if you can't talk
to any of the (other) devices on it.  I'd sure like to be able to write my
own tape backup software or an ethernet driver.  Especially if I can write
it once, and know that it'll work with all of the SCSI host adaptors that
are/will be available.


Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
University of Maryland, Computer Science Center - Systems Programming