This message is from the T13 list server.
On Fri, 12 Apr 2002 07:46:25 -0600, Pat LaVarre wrote: >This message is from the T13 list server. >Offline I've seen the claim that nearly all actual Atapi >devices, if intepreted per Ansi, You mean interpreted per T10 MMC-x, correct? Because T13 doesn't describe the SCSI command set for any ATAPI device. >TELL the host to use SFF rather than Ansi. Specifically, this >claim says that ... In response to the standard, start of life, >plug 'n play query of `plscsi -v -x 12 0 0 0 24 0 -i x24`, most >actual Atapi devices copy in x00 as the byte at offset 2. OK. So this is what a certain SCSI subset, the subset we call ATAPI, should do for this command? If T10 does not recognize this subset then what does that mean? >Ansi T13 had no comment on what this means, last I checked. Again T13 doesn't have anything to do with SCSI command sets. For SCSI devices using the ATA/ATAPI interface as the SCSI physical transport layer, T13 only defines the ATA/ATAPI physical transport and PACKET command protocol. >Ansi T10 says this is an op x12 Inquiry of up to x24 bytes. >(That's close to real - it should copy in x24 bytes always.) >Ansi T10 says x00 at offset 2 means the device "may or may not" >comply with any particular Ansi standard. OK. Sounds like a prefectly valid thing for T10 to say. >SFF says SFF-compliant devices shall put a x00 there. OK. I'm sure that is because SFF-8020 was an attempt by a few individuals to redefine SCSI to their way of thinking. I think we can safely say these people failed, SFF-8020 is now very obsolete. ATAPI device should be implemented according to the appropriate SCSI command set documents, such as MMC-x. That means such device would not be putting 0x00 in this Inquiry data byte. >I'd love to hear people evaluate this claim. Does anyone on >Earth know of Atapi devices that don't put a zero there? Don't know... Good question. *** Hale Landis *** www.ata-atapi.com ***
