Contradiction between MMC and Fuji on Inquiry command standard response

David Burg daviburg at windows.microsoft.com
Wed Apr 2 11:13:21 PDT 2008


Formatted message: <A HREF="r0804024_f.htm">HTML-formatted message</A>
Attachment #1: <A HREF="r0804024_image001.png">image001.png</A>

Hi MMC and Fuji,
Final MMC 5 says:
Table 320 - INQUIRY Data for ATAPI and USB Drives
Response Data Format 0011b
HiSup 0b
NormACA 0b
However, Mt Fuji 6 and 7 says:
[cid:image001.png at 01C894B1.BB2DC3C0]
The ATAPI Transport Version field shall contain 03h to comply with this
version of the Specification. This field
indicates the version of the ATAPI Transport that is being used. For more
information on the transport, see the INCITS
T13/1153D standard. For a SCSI logical unit this field is defined by the SCSI
SPC-2 standard.
A Response Data Format value of 02h indicates that the data shall be in the
format specified in this Specification.
Response Data Format values less than two are obsolete. Response Data Format
values greater than two are
reserved.
-*-
Note: A value of 3 for ATAPI Transport Version would match NormACA 1b and
HiSup 1b. The response data format values contradict as well.
Our Microsoft WLK test is currently verifying versus the MMC requirement
above, thus the Fuji compliant devices get failed. Standard committees, which
is the right specification here?
Also, how does the host know if it should decode according to SCSI or
according to ATAPI for the Fuji specification of inquiry response?
With regards,
David Burg.



More information about the T10 mailing list