🚀 go-pugleaf

Whoa, now the Mach prospective porters are hitting a topic close to my heart.
We should standardize on a SCSI API.  I would like to have this, not just
for inter-computer (host-to-host) data transfer, but also for all the neat
new SCSI peripherals, such as scanners, that are coming out.

In my opinion, we should have an API in the kernel which is a device driver
and provides only very simple services.  The disk device driver should go
through that device driver... it should be possible for me to send any
CDB and get results.  The driver could internally handle disconnects and
reconnects without bothering me about it.  Something like ASPI, but more
convenient; or something like the RAW command in the PC532 monitor, which
is really nice.

Also, it might be good to use the Adaptec chip for the external SCSI port,
and leave the other chip for local drives.  (Hm, this contradicts what I
said above)  That is to say, the Adaptec chip device driver would have
read/write/ioctl access for non-file-system peripherals such as tape,
scanner, etc. that would be controlled by application software.  Then if
something clobbers the external bus the system stays up.

Supposedly ANSI has defined a "Common Access Method" (CAM) specification
which says how SCSI should look to application code.  Anyone have a copy
and any comments on it?