Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: SCSI disks
Message-ID: <7195@cbmvax.UUCP>
Date: 1 Jul 89 01:24:49 GMT
References: <6560@cs.Buffalo.EDU>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 16

In article <6560@cs.Buffalo.EDU> ugkamins@marvin.cs.buffalo.edu (Dr. R. Chandra) writes:
>Also, has anyone developed a general device driver for
>SCSI?  One could OpenDevice(SCSI_NAME, SCSI_dev_num, &IOReqBlk, 0) and
>address any physical device number attached to the interface.  Are the
>commands the same to write/read/etc. to all devices?  I thought they would be.
>Of course, each device will have its own specific private commands (it
>wouldn't be appropriate to format a compact disc, at least not until
>writable ones are more prevalent, such as THOR).

	THe new scsidirect spec covers this and does what you want.  The
A590, A2091 (NOT A2090A yet, maybe sometime soon), Microbotics HF, GVP, and
one or two others support the spec.  More will, hopefully (like the A2090).
It allows sending scsi commands/data/etc, getting error codes back, etc.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup