SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001StandardSSA-TL1 ANSI X3.295:1996SSA-TL1 T10.1/0989 revision 10bSSA-TL2 (no version claimed)SSA-TL2 ANSI NCITS.308:1998SSA-TL2 T10.1/1147 revision 05bSSC (no version claimed)SSC ANSI NCITS.335:2000SSC T10/0997 revision 22SSC T10/0997 revision 17SSC-2 (no version claimed)SST (no version claimed)Version Descriptor Not Supported or No Standard Identified7.3.3 SCSI Parallel Interface specific INQUIRY dataTable 51 — Version descriptor values (part 5 of 5)Annex C contains the version descriptor value assignments in numeric order.085Ch085Bh0820h083Ch083Bh0200h021Ch0207h0201h0360h0920h0000hPortions of bytes 6 and 7 and all of byte 56 of the standard INQUIRY data shall be used only by the SCSI ParallelInterface. These fields are noted in table 46. For details on how the SPI-specific fields relate to the SCSI ParallelInterface see SPI-n (where n is 2 or greater). Table 52 shows just the SPI-specific standard INQUIRY fields. Thedefinitions of the SCSI Parallel Interface specific fields shall be as follows.Table 52 — SPI-specific standard INQUIRY bitsVersionDescriptorValueBitByte7 6 5 4 3 2 1 06 see table 46 ADDR167 see table 46 WBUS16 SYNC see table 46 Obsolete see table 46...56 Reserved CLOCKING QAS IUSA wide SCSI address 16 (ADDR16) bit of one indicates that the target supports 16-bit wide SCSI addresses. Avalue of zero indicates that the device does not support 16-bit wide SCSI addresses.A wide bus 16 (WBUS16) bit of one indicates that the target supports 16-bit wide data transfers. A value of zeroindicates that the device does not support 16-bit wide data transfers.A synchronous transfer (SYNC) bit of one indicates that the target supports synchronous data transfer. A value ofzero indicates the device does not support synchronous data transfer.The obsolete bit 2 in byte 7 indicates whether the target supports an obsolete data transfers managementmechanism defined in SPI-2.90 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20Table 53 defines the relationships between the ADDR16 and WBUS16 bits.Table 53 — Maximum logical device configuration tableADDR16 WBUS16 Description0 0 8 bit wide data path on a single cable with8 SCSI IDs supported0 1 16 bit wide data path on a single cablewith 8 SCSI IDs supported1 1 16 bit wide data path on a single cablewith 16 SCSI IDs supportedThe CLOCKING field shall not apply to asynchronous transfers and is defined in table 54.Table 54 — CLOCKING fieldCode00b01b10b11bDescriptionIndicates the device server supports only STIndicates the device server supports only DTReservedIndicates the device server supports ST and DTA quick arbitration and selection supported (QAS) bit of one indicates that the device server supports quickarbitration and selection. A value of zero indicates that the device server does not support quick arbitration andselection.An information units supported (IUS) bit of one indicates that the device server supports information unit transfers.A value of zero indicates that the device server does not support information unit transfers.NOTE 14 The acronyms ST and DT and the terms 'quick arbitration and selection' and 'information units' aredefined in SPI-3, SPI-4, and possibly later revisions of the SCSI parallel interface standard.7.3.4 Vital product dataThe application client requests the vital product data information by setting the EVPD bit to one and specifying thepage code of the desired vital product data. See 8.4 for details about vital product data. The information returnedconsists of configuration data (e.g., vendor identification, product identification, model, serial number), manufacturingdata (e.g., plant and date of manufacture), field replaceable unit data and other vendor specific or devicespecific data. If the device server does not implement the requested page it shall return CHECK CONDITIONstatus. The a sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to INVALIDFIELD IN CDB.NOTES15 The device server should have the ability to process the INQUIRY command even when an error occurs thatprohibits normal command completion. In such a case, CHECK CONDITION status should be returned forcommands other than INQUIRY or REQUEST SENSE. The sense data returned may contain the fieldreplaceable unit code. The vital product data may be obtained for the failing device using the INQUIRYcommand.16 This standard defines a format that allows device-independent application client software to display the vitalproduct data returned by the INQUIRY command. The contents of the data may be vendor specific, and maybe unusable without detailed information about the device.17 This standard does not define the location or method of storing the vital product data. The retrieval of the datamay require completion of initialization operations within the device, that may induce delays before the data isdpANS SCSI Primary Commands - 2 (SPC-2) 91
Page 1 and 2:
dpANSProjectT10/1236-DRevision 2018
Page 3:
DraftANSI (r)NCITS.351:200xAmerican
Page 6 and 7:
T10/1236-D Revision 20 18 July 2001
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59: T10/1236-D Revision 20 18 July 2001
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
show all

SCSI Primary Commands - 2.pdf

Create successful ePaper yourself

Delete template?

Save as template?