In message <20000202010204.A40068@panzer.kdm.org>, ken@kdm.org writes:
>On Tue, Feb 01, 2000 at 22:40:26 -0700, Drew Eckhardt wrote:
>> In the SCSI-1 spec that some of this conformed to, Read-6 was required.
>> Read-10 was suggested as a good idea. Since some devices Wedged until
>> power cycled when fed a command they didn't support, I figured that
>> using Read-6 until we absolutely positively had to use Read-10 was a
>> fine idea.
>FWIW, even in the SCSI-1 spec, 10-byte reads were mandatory for CDROM and
>WORM devices, and 6-byte reads were optional. (It is that way in the
>SCSI-2 spec, and I think in the MMC specs as well.)
I worked off the X3T9.2 REV 17B draft.
It covers Direct Access devices, Sequential Access devices, and Printers.
In each section, there are tables of 6 and 10 byte supported commands. In
the Direct Access section we have the following:
Key: M = Command implementation is mandatory.
E = Command implementation is required for SCSI devices that support
device-independent self-configuring software.
Table 8-1
Group 0 Commands for Direct-Access Devices
==============================================================================
Operation
Code Type Command Name Section
------------------------------------------------------------------------------
08H M READ 8.1.4
Table 8-22
Group 1 Commands for Direct-Access Devices
28H E READ 8.2.2
>The way we handle this in FreeBSD is to specify a minimum command size in
>the function that builds read and write CCBs.
Under Linux, the CD and disk drivers are completely divorced. When I
wrote the disk driver, I used the smallest command possible for a given
transfer size. The CD driver was cloned from that.
They should probably share a common direct-access support file that
does that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Feb 07 2000 - 21:00:08 EST