Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!rutgers!ames!ptsfa!ihnp4!mb2c!gamma!ulysses!sfmag!sfsup!perry
From: perry@sfsup.UUCP (P.S.Kivolowitz)
Newsgroups: comp.sys.amiga
Subject: Re: SCSI device drivers
Message-ID: <1347@sfsup.UUCP>
Date: Tue, 21-Apr-87 13:41:11 EST
Article-I.D.: sfsup.1347
Posted: Tue Apr 21 13:41:11 1987
Date-Received: Thu, 23-Apr-87 04:09:50 EST
References: <1548@umd5.umd.edu>
Distribution: na
Organization: AT&T-IS, Summit N.J. USA
Lines: 22

In article <1548@umd5.umd.edu>, louie@sayshell.umd.edu.UUCP writes:
> 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?
> 

By design, the ASDG disk processor will be partitioned as you suugest. There
will be some DOS compatible hooks for AmigaDOS to get access to file systems
out on the drives as well as  a  complete lower layer which talks high level
commands to and from the controller.

(Remember that the ASDG Smart Disk Processor (SDP) is a computer in its own
right every bit as powerful as the  Amiga  itself. We would be remiss if we
did not allow users to capitalize upon this.)

Perry S. Kivolowitz