September 11, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 3 changes:
|
|
- Shauna Blake
- 5 years ago
- Views:
Transcription
1 September 11, ArrowsWest Drive Colorado Springs, CO To: From: Subj: T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Revision 3 changes: 1. Required the initiator to set the DISCPRIV bit in the IDENTIFY message to 0 (was just recommended). 2. Clarified that expander addresses are specific to each initiator. 3. the RECEIVER TIMING SKEW field in the MARGIN CONTROL and MARGIN REPORT SEDBs. 4. Added a second Vendor Specific field in the MARGIN CONTROL and MARGIN REPORT SEDBs. 5. Clarified that the reset far port function occurs upon the next BUS FREE phase on the near port. 6. Added a device type (D_CLASS) field to the first byte of the SEDB to report the device type that set the USED bit to one. 7. Changed the SEDB rules to apply to initiators and communicative expanders. Targets are not covered by this revision of ECP, but could be added in the future. 8. Changed 'target port' to 'far port' in the MARGIN CONTROL and MARGIN REPORT SEDBs. I received a request to include the ability to report skew compensation and AAF settings. I have not yet done so, but expect that this could be done with an inbound single function. While the values for these settings are likely to be vendor specific, I think we could standardize the number of fields and the size of the fields. I am especially looking for input on how big to make these fields. I have documented the ECP proposal in the form of an annex for SPI-4 on the following pages. Page 1 of 14
2 Annex X (normative) X.1 Introduction This annex describes a method of expander communication and topology discovery called Expander Communication Protocol (ECP). This protocol permits application clients to detect expanders that support the protocol. It also permits the application client to pass parameter settings to expanders and permits expanders to report settings and status information. No new hardware features are required of initiators or targets to implement this protocol. ECP depends on the expander being able to monitor the data transfers associated with WRITE BUFFER and READ BUFFER commands (see SPC-2) and to alter specific portions of the data transferred as it passes through the expander in either direction. To simplify the expander implementation requirements, ECP is restricted to 8-bit asynchronous transfers. X.2 Glossary and Definitions X.2.1 Communicative expander: A simple expander (see Annex F) that has the additional capability to support the requirements of this annex and thus is capable of transmitting information beyond that received on its ports to specific other entities in the domain. In this annex, unless stated otherwise, the term expander means communicative expander. X.2.2 Expander function signature: A specific sequence of data bytes that identifies an ECP function in the data phase of a WRITE BUFFER or READ BUFFER command. X.2.3 Far port: For the current I/O process, an expander port that is not the near port. X.2.4 First expander: In a series expander set, the expander that couples the bus segment containing the initiator to the next bus segment on the path to the target. X.2.5 Last expander: In a series expander set, the expander that couples the bus segment containing the target to the next bus segment on the path to the initiator. X.2.6 Near port: For the current I/O process, the expander port connected directly to the initiator through a bus segment or connected to the initiator through other expanders and bus segments. X.2.7 Non-target port: A far port (X.2.7) that is not a target port (X.2.11). That is, all far ports that do not include the target for this I/O process. X.2.8 target. X.2.9 n th expander: In a series expander set, the n th expander on the path from the initiator to the Path: The set of all bus segments and expanders between an initiator and a target. X.2.10 Series expander set: The set of one or more expanders that couple the bus segment containing an initiator to the bus segment containing a target. X.2.11 Target port: For the current I/O process, a far port that is connected directly to the target through a bus segment or connected to the target through other expanders and bus segments. Page 2 of 14
3 X.3 Enabling ECP Following a power cycle or bus reset, a communicative expander shall function as a simple expander for each initiator until the initiator enables ECP as follows: 1. Negotiate asynchronous transfer mode and a transfer width of 8 bits to some target device 2. Issue a WRITE BUFFER command to the same target device with the MODE field set to Echo buffer plus enable ECP (1Ah). The initiator may disable ECP by: 1. Negotiate asynchronous transfer mode and a transfer width of 8 bits to some target device 2. Issue a WRITE BUFFER command to the same target device with the MODE field bit set to Disable ECP (1Bh). [Editor's Note: This proposal would expand the MODE field in the WRITE BUFFER command (SPC-2) from 4 bits to 5 bits adding the above two code values and reserving all other new code values. These values were selected so that enabling ECP and writing to the echo buffer can be combined in one operation with MODE 1Ah. Legacy device servers may interpret this value as either Echo buffer (0Ah) or Write data (02h), which should cause no harm. Legacy device servers may interpret the Disable ECP code value as either 0Bh or 03h, both of which are reserved and should cause no harm.] This enabling and disabling of ECP is done on an initiator basis (i.e., each initiator issues a single WRITE BUFFER command to enable or disable ECP for that initiator for all communicative expanders on the bus). The enabling or disabling of ECP occurs regardless of the device server's response to the WRITE BUFFER command. (Legacy device servers may return CHECK CONDITION status and ILLEGAL REQUEST sense key because they implemented a smaller MODE field.) Note: While the initiator has ECP enabled, it is responsible for not issuing WRITE BUFFER commands with the EXPANDER FUNCTION SIGNATURE in the first 7 bytes of the data buffer unless it is an expander function header (see X.4). X.4 Communicative expander function structures Communicative expander functions consist of outbound and inbound functions. The outbound functions are contained in the data of a WRITE BUFFER command with the MODE field set to Write data (00010b), Echo buffer mode (01010b) or Echo buffer plus enable ECP mode (11010b). The inbound functions return information in the data of a READ BUFFER command with the mode field set to Data (00010b), Echo buffer mode (01010b) or Echo buffer plus enable ECP mode (11010b). The initiator shall not enable disconnects for these WRITE BUFFER and READ BUFFER commands. That is, the DISCPRIV bit in the IDENTIFY message (see ) shall be set to 0. The outbound and inbound functions are further divided into multiple and single functions. For multiple functions, the data is transferred in a 172-byte data structure consisting of a 16-byte expander function header followed by ten 16-byte short expander descriptor blocks (SEDB). For single functions, the data is transferred in a data structure whose length depends on the function. This data structure consists of a 16-byte expander function header followed by a one long expander descriptor block (LEDB). In either case, the first 16 bytes of the data structure contain an expander function header as shown in table X.1. Page 3 of 14
4 Table X.1 Expander function header 0 (MSB) EXPANDER FUNCTION SIGNATURE (B73384B8508F27h) 5 6 (LSB) 7 INITIATOR SCSI ADDRESS 8 EXPANDER FUNCTION CODE Function specific The EXPANDER FUNCTION SIGNATURE contains a code of B73384B8508F27h that signifies this WRITE BUFFER or READ BUFFER data is an expander function. The application client shall set the INITIATOR SCSI ADDRESS field to the SCSI address of the initiator. The expander shall check that this field matches the SCSI address for the initiator of the current I/O process. If both the EXPANDER FUNCTION SIGNATURE is correct and the INITIATOR SCSI ADDRESS field matches the initiator's SCSI address, then this WRITE BUFFER or READ BUFFER data is an expander function and shall be processed by the expander. Otherwise, is a normal WRITE BUFFER or READ BUFFER command and shall be repeated by communicative expanders but otherwise shall be ignored. The EXPANDER FUNCTION CODES are documented in table X.2. The function-specific bytes are documented for single functions in X.5.2 and X.5.4. The function-specific bytes are not presently used for multiple functions and are reserved for future use. Page 4 of 14
5 Table X.2 Expander functions EXPANDER FUNCTION CODE 00h 01h 02h - 2Fh 30h - 3Fh 40h 41h - 6Fh 70h - 7Fh 80h 81h 82h 83h - AFh B0h - BFh C0h C1h - EFh F0h - FFh Expander function ASSIGN ADDRESS MARGIN CONTROL Vendor specific CONTROL Vendor specific MARGIN REPORT REPORT CAPABILITIES Vendor specific EXPANDER INQUIRY Vendor specific Type Outbound multiple function Outbound single function Inbound multiple function Inbound single function The outbound multiple functions are documented in X.5.1 and the outbound single functions are documented in X.5.2. The inbound multiple functions are documented in X.5.3 and the inbound single functions are documented in X.5.4. For outbound and inbound multiple functions, the expander function header is followed by ten short expander descriptor blocks as shown in table X.3. For outbound and inbound single functions, the expander function header is followed by one long expander descriptor block documented in X.5.2 and X.5.4. Table X.3 Short expander descriptor block (SEDB) 0 USED D_CLASS Function-specific fields The USED bit is documented in X.5.1.1, X.5.2.1, X.5.3.1, and X Page 5 of 14
6 The D_CLASS field identifies the device class that set the USED bit to one as defined in table X.4: Table X.4 Device class D_CLASS 000b 001b 010b 011b - 111b Device class Communicative expander device SCSI Initiator device The remaining fields in the short expander descriptor block are specific to the expander function and are documented in X.5. X.5 Expander functions X.5.1 Outbound multiple functions X Outbound multiple function data transfer rules Outbound multiple functions shall be performed during a WRITE BUFFER command with the MODE field set to one of the three values specified in X.4. The initiator shall transfer an expander function header followed by ten short expander descriptor blocks (SEDB). The application client may use an SEDB to indicate the initiator's parameters or settings. If the application client uses an SEDB, it shall use the first SEDB and shall set the USED bit in the first SEDB to 1. The application client shall set the USED bit to 0 in all unused SEDBs. Each expander in the domain shall repeat the entire data structure without alteration to its target port, if any, except the expander shall alter the first SEDB encountered with a USED bit of 0. In this SEDB, the expander shall change the USED bit to 1, shall set the D_CLASS field as described in table X.4, and shall output 0 bits in the reserved field of the first byte. The remaining 15 bytes of this SEDB shall be repeated without alteration. The expander shall interpret the other fields of this altered SEDB as described below for the EXPANDER FUNCTION CODE. Each expander in the domain shall either repeat the data received on the near port or shall repeat the data output to the target port on all far ports that are not part of the I_T nexus. An expander that receives a reserved or unimplemented vendor-specific multiple EXPANDER FUNCTION CODE shall follow all of the rules in this sub-clause, but shall ignore the contents of the altered SEDB. X ASSIGN ADDRESS The ASSIGN ADDRESS expander function is used to assign an expander address to one or more expanders for this initiator. The expander address is specific to the assigning initiator. The expander address assigned by one initiator has no affect on the expander addresses assigned by other initiators. The SEDB for this expander function is shown in table X.5. Page 6 of 14
7 Table X.5 ASSIGN ADDRESS SEDB 0 USED D_CLASS 1 ASSIGN EXPANDER ADDRESS The ASSIGN bit of 1 indicates that the expander shall respond to the expander address specified in the EXPANDER ADDRESS field for single functions from this initiator. The address assignment shall remain in effect until changed by another ASSIGN ADDRESS function from this initiator or until the next reset condition or power cycle. An ASSIGN bit of 0 indicates that the expander shall not change its expander address assignment for this initiator. Assigning the expander address b to an expander shall indicate that it has no expander address assigned for this initiator. The application client shall not use expander address b in single functions. X MARGIN CONTROL The MARGIN CONTROL expander function sets various parameter settings in the initiator or expander for usage between the initiator-target pair on subsequent synchronous and paced transfers. These parameter settings shall remain in effect until changed by another MARGIN CONTROL expander function or by a reset condition. The MARGIN CONTROL SEDB is shown in table X.6. Page 7 of 14
8 Table X.6 MARGIN CONTROL SEDB 0 USED D_CLASS 1 DRIVER STRENGTH (near port) 2 SIGNAL GROUND BIAS (near port) DRIVER PRECOMPENSATION (near port) 3 SLEW RATE (near port) Vendor specific (near port) Vendor specific (near port) 8 9 DRIVER STRENGTH (far port) 10 SIGNAL GROUND BIAS (far port) DRIVER PRECOMPENSATION (far port) 11 SLEW RATE (far port) Vendor specific (far port) Vendor specific (far port) Two sets of margin control fields (DRIVER STRENGTH, SIGNAL GROUND BIAS, DRIVER PRECOMPENSATION, and SLEW RATE) are provided, one set for the near port and another set for the far port. If the first SEDB is used for the initiator settings, only the far port fields are used; the near port fields are reserved. The margin control fields shall be implemented as two's-complement values with 0000b being the nominal value. The maximum supported setting for each field shall be 0111b and the minimum supported setting for each field shall be 1111b. Up to 16 distinct values are available for each field. Devices that support fewer than 16 distinct values for a field should round non-supported settings to a supported value. In the case of the SIGNAL GROUND BIAS fields, values 0000b through 0111b shall enable the bias cancellation circuit and values 1000b through 1111b shall disable the bias cancellation circuit, if disabling of this circuit is supported. X.5.2 Outbound single functions X Outbound single function data transfer rules Outbound single functions shall be performed during a WRITE BUFFER command with the MODE field set to one of the three values specified in X.4. The initiator shall transfer an expander function header followed by a long expander descriptor block (LEDB). Each expander in the domain shall repeat the entire data structure without alteration to its target port, if any, except if the EXPANDER ADDRESS field in the first byte of the LEDB matches its currently assigned expander address for this initiator (see X.5.1.5) and the USED bit is 0. In this case, the expander shall change the USED bit to 1 and shall output its currently assigned expander address for this initiator in the EXPANDER ADDRESS field. The expander shall interpret the other fields of this altered LEDB as described below for the EXPANDER FUNCTION CODE. Each expander in the domain shall either repeat the data received on the near port or shall repeat the data output to the target port on all far ports that are not part of the I_T nexus. Page 8 of 14
9 An expander that receives a reserved or unimplemented vendor-specific single EXPANDER FUNCTION CODE shall follow all of the rules in this sub-clause, but shall ignore the contents of the altered LEDB. X CONTROL The CONTROL function is used to set or clear parameters on the addressed expander. The functionspecific bytes in the expander function header are reserved for this function. The SEDB for the CONTROL function is shown in table X.7. Table X.7 CONTROL data structure 0 USED EXPANDER ADDRESS 1 TARGET_ADRS 2 FAR_CTL The TARGET_ADRS field shall be set to the SCSI address of a target on one of the expander's far ports. This identifies which far port is to be controlled on expanders that have multiple far ports. If the specified TARGET_ADRS does not match a known target SCSI address on one of the expander's far ports, then the expander shall perform no far port control action on any port. The FAR_CTL field is defined as shown in table X.8. Table X.8 FAR_CTL field values FAR_CTL 000b 001b 010b 100b all other values Far port control action No operation Disable far port Enable far port Reset far port A far port control action of no operation shall have no effect on the specified far port. A far port control action of disable far port shall cause the expander to stop repeating signals to the specified far port and shall cause the expander to ignore signals from the specified far port upon the next BUS FREE phase. Page 9 of 14
10 A far port control action of enable far port shall cause the expander to resume repeating signals to the specified far port and shall cause the expander to resume responding to signals from the specified far port upon the next BUS FREE phase. A far port control action of reset far port shall cause the expander to create a hard reset condition on the specified far port upon the next BUS FREE phase on the near port (i.e., the expander creates a pulse on the RST signal). The expander shall not propagate this hard reset condition to any other of its ports. X.5.3 Inbound multiple functions X Inbound multiple function data transfer rules The application client shall set the USED bit in each of the short expander descriptor blocks (SEDB) to 0. The data structure containing an inbound multiple function is then placed in the target's buffer using a WRITE BUFFER command with the MODE field set to one of the three values specified in X.4. Expanders shall not alter the data structure during the WRITE BUFFER command if the EXPANDER FUNCTION CODE is 80h to FFh. The inbound multiple function is then performed during a subsequent READ BUFFER command with the MODE field set to one of the three values specified in X.4. During the data transfer phase of the READ BUFFER command, each expander with a target port shall repeat the entire data structure without alteration to its near port, except the expander shall alter the first SEDB encountered with a USED bit of 0. In this SEDB, the expander shall change the USED bit to 1, shall set the D_CLASS field as described in table X.4, and shall output 0 bits in the reserved field of the first byte. The remaining 15 bytes of this SEDB shall be output as described below for the EXPANDER FUNCTION CODE. Each expander in the domain shall either repeat the data received on the target port or shall repeat the data output to the near port on all far ports that are not part of the I_T nexus. An expander that receives a reserved or unimplemented vendor-specific multiple EXPANDER FUNCTION CODE shall follow all of the rules in this sub-clause, but shall output 00h in bytes 1 through 15 of the altered SEDB. X MARGIN REPORT The MARGIN REPORT expander function is used to report the current margin settings for the initiator, expander, or target. The MARGIN REPORT SEDB is shown in table X.9. Page 10 of 14
11 Table X.9 MARGIN REPORT SEDB 0 USED D_CLASS 1 DRIVER STRENGTH (near port) 2 SIGNAL GROUND BIAS (near port) DRIVER PRECOMPENSATION (near port) 3 SLEW RATE (near port) Vendor specific (near port) Vendor specific (near port) 8 9 DRIVER STRENGTH (far port) 10 SIGNAL GROUND BIAS (far port) DRIVER PRECOMPENSATION (far port) 11 SLEW RATE (far port) Vendor specific (far port) Vendor specific (far port) Two sets of margin report fields (DRIVER STRENGTH, SIGNAL GROUND BIAS, DRIVER PRECOMPENSATION, and SLEW RATE) are provided, one set for the near port and another set for the far port. If the last SEDB is used to communicate initiator settings to the application client, only the far port fields are used; the near port fields are reserved. In this case, the initiator should set the USED bit to 1 in this SEDB before returning the data buffer to the application client. The margin report fields shall return the current settings for the initiator-target pair. Fields that are not implemented shall be reported as 0000b. Otherwise, the current setting for the field, possibly rounded as described in X.5.1.3, shall be returned. X REPORT CAPABILITES The REPORT CAPABILITES function is used to determine domain topology and report expander characteristics. The REPORT CAPABILITES SEDB is shown in table X.10. Page 11 of 14
12 Table X.10 REPORT CAPABILITES SEDB 0 USED D_CLASS 1 (MSB) FAR SCSI ID LIST 2 (LSB) 3 MINIMUM TRANSFER PERIOD FACTOR 4 5 MAXIMUM REQ/ACK OFFSET 6 MAXIMUM TRANSFER WIDTH EXPONENT 7 PROTOCOL OPTION BITS SUPPORTED 8 PORTS TARG_MODE The FAR SCSI ID LIST field contains the inclusive OR of all SCSI IDs known to be located on the target port of the expander. For example, if SCSI devices with IDs 0, 1, and 12 were previously accessed on the target port, the expander sets this field to 1003h. The MINIMUM TRANSFER PERIOD FACTOR field shall be set to the smallest value of the TRANSFER PERIOD FACTOR (see ) supported by the expander. The MAXIMUM REQ/ACK OFFSET field shall be set to the largest value of the REQ/ACK OFFSET (see ) supported by the expander. The MAXIMUM TRANSFER WIDTH EXPONENT field shall be set to the largest value of the TRANSFER WIDTH EXPONENT (see ) supported by the expander. The PROTOCOL OPTIONS BITS SUPPORTED field shall set the corresponding bit to one for each supported protocol option bit in byte 7 of the PPR message (see ). The PORTS field shall contain the number of ports on the expander not including the near port. A value of 0 in this field indicates that the expander is not capable of reporting this information. The TARG_MODE field specifies the current bus mode for the target port as defined in table X.11. Table X.11 Far port bus mode TARG_MODE 00b 01b 10b 11b Target port bus mode Unknown (expander not capable of reporting bus mode) Single ended Low Voltage Differential High Voltage Differential Page 12 of 14
13 X.5.4 Inbound single functions X Inbound single function data transfer rules The application client shall set the USED bit in the long expander descriptor block (LEDB) to 0. The data structure containing an inbound single function is then placed in the target's buffer using a WRITE BUFFER command with the MODE field set to one of the three values specified in X.4. Expanders shall not alter the data structure during the WRITE BUFFER command if the EXPANDER FUNCTION CODE is 80h to FFh. The inbound single function is then performed during a subsequent READ BUFFER command with the MODE field set to one of the three values specified in X.4. During the data transfer phase of the READ BUFFER command, each expander with a target port shall repeat the entire data structure without alteration to its near port, except if the EXPANDER ADDRESS field in the first byte of the LEDB matches its currently assigned expander address (see X.5.1.5) and the USED bit is 0. In this case, the expander shall change the USED bit to 1 and shall output its currently assigned expander address in the EXPANDER ADDRESS field. The expander shall output the remaining bytes of this LEDB as described below for the EXPANDER FUNCTION CODE. Each expander in the domain shall either repeat the data received on the target port or shall repeat the data output to the near port on all far ports that are not part of the I_T nexus. An expander that receives a reserved or unimplemented vendor-specific single EXPANDER FUNCTION CODE shall follow all of the rules in this sub-clause, but shall output 00h in remaining bytes of the altered LEDB. X EXPANDER INQUIRY The EXPANDER INQUIRY function is used to report information about the specified expander in a manner similar to the SCSI INQUIRY command documented in SPC-2. The expander function header for this function shall include function specific fields as described in table X.12. Table X.12 EXPANDER INQUIRY expander function header 0 (MSB) EXPANDER FUNCTION SIGNATURE (B73384B8508F27h) 5 6 (LSB) 7 INITIATOR SCSI ADDRESS 8 EXPANDER INQUIRY FUNCTION CODE (C0h) 9 EVPD 10 PAGE CODE ALLOCATION LENGTH An enable vital product data (EVPD) bit of one specifies that the expander shall return the optional vital product data specified by the PAGE CODE field (see the vital product data parameters documentation in SPC-2). If the expander does not support the optional vital product data, then it shall return all zero bytes Page 13 of 14
14 for the specified allocation length. If the EVPD bit is zero, then the expander shall return Expander INQUIRY data as documented in table X.13. Table X.13 EXPANDER INQUIRY data 0 USED ADDRESS ADDITIONAL LENGTH (33h) (MSB) VENDOR IDENTIFICATION 15 (LSB) 16 (MSB) PRODUCT IDENTIFICATION 31 (LSB) 32 (MSB) PRODUCT REVISION LEVEL 35 (LSB) Vendor-specific The VENDOR IDENTIFICATION, PRODUCT IDENTIFICATION, and PRODUCT REVISION LEVEL fields shall return data as documented in SPC-2 for the Standard INQUIRY data format. X.6 Data Transfer Requirements The communicative expander functions shall only be performed when the data transfer agreement is 8-bit asynchronous. For any other data transfer agreement, the communicative expander shall operate as a simple expander. When altering data, communicative expanders shall construct correct parity for the altered data on the outgoing port. Page 14 of 14
August 14, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 1 changes:
August 14, 2000 4420 ArrowsWest Drive Colorado Springs, CO 80907 To: From: Subj: T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol Revision 1 changes:
Overview of operation
July 7, 2000 To: T10 Technical Committee From: Ron Roberts, Adaptec, Inc. Subj: Additional Expander Proposal This proposal contains corrections and additions as well as modified section of SDVR02. Discussions
1 Overview. T10/ revision 0
Date: 10/22/08 To: T10 Committee (SCSI) From: George Penokie (LSI) Subject: SPC-4: Cache hits and power on statistics 1 Overview There are some performance statistics relating to cache hits that would
1 Overview. 2 Changes to SPC-4. T10/ revision 5
Date: 3/18/09 To: T10 Committee (SCSI) From: George Penokie (LSI) Subject: SPC-4: Cache hits and power on statistics 1 Overview There are some performance statistics relating to cache hits that would be
06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) 21 June 2006
To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com) Date: 21 June 2006 Subject: 06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) Revision history Revision
04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 29 October 2004 Subject: 04-352r0 SAS-1.1 Phy test functions for SMP Revision history Revision 0 (29 October 2004) First revision
The next page shows the questions asked in revision 0 of this proposal and the answers supplied by the May SCSI Working Group meeting.
T10/99-163r1 Date: 13 May 1999 To: T10 Technical Committee From: Ralph Weber, LSI Logic Alternate Member of T10 Subj: EXTENDED COPY command for SPC-2 This revision contains those changes agreed by the
T10/99-295r4. 4/24/2000 John Lohmeyer T10 Chairman. Subject: Proposal for Enhanced signalling to be included in SPI-4
T10/99-295r4 Seagate Technology Tel: 405-324-3070 10323 West Reno (West Dock) Fax: 405-324-3794 Oklahoma City, OK 73127-9705 gene_milligan@notes.seagate.com P.O. Box 12313 Oklahoma City, OK 73157-2313
10.2 SCSI application layer
2 November 2007 07-479r0 SAS-2 Phy test pattern transmitter controls To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 November 2007 Subject: 07-479r0 SAS-2 Phy test pattern transmitter
Related Documents ses2r00 - SCSI Enclosure Services - 2 revision r0 - SES-2 INVOP for Threshold In page
To: T10 Technical Committee From: Dennis Spicher (dennis.spicher@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 18 July 00 Subject: Revision History Revision 0 (8 June 00) first revision Revision 1
The Tape Library Experts TM RLS. SCSI Interface Reference Rev. B
The Tape Library Experts TM RLS SCSI Interface Reference 501551 Rev. B Notice Information contained in this document is copyrighted by Qualstar Corporation. It is intended for use by Qualstar's customers
06-037r3 SAS-2 SMP Lists (DISCOVER LIST) 28 April, 2006
To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com), Brad Besmer LSI Logic Date: 28 April, 2006 Subject: 06-037r3 SAS-2 SMP Lists (DISCOVER LIST) Revision history Revision
Intel Storage System JBOD 2000S3 Product Family
Intel Storage System JBOD 2000S3 Product Family SCSI Enclosure Services Programming Guide SES Version 3.0, Revision 1.8 Apr 2017 Intel Server Boards and Systems Headline
T10/03-183r1 page 1. New Inquiry VPD Page Management Network Address
T10/03-183r1 page 1 Date: 6/26/03 T10: T10 Technical Committee (SCSI) From: Subject: Charles Binford, Sun Microsystems, Inc, (charlesbinford@suncom) Paul von Behren, Sun Microsystems, Inc, (paulvonbehren@suncom)
06-037r5 SAS-2 SMP Lists (DISCOVER LIST) 1 May, 2006
To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com), Brad Besmer LSI Logic Date: 1 May, 2006 Subject: 06-037r5 SAS-2 SMP Lists (DISCOVER LIST) Revision history Revision 0
FCD Information Technology - Small Computer System Interface - Part 381: Optical Memory Card Device Commands (SCSI OMC)
Final Committee Draft IS/IEC JTC 1/SC 25N 533 1998-12-10 FCD 14776-381 Information Technology - Small Computer System Interface - Part 381: ptical Memory Card Device Commands (SCSI MC) Contents... Page
COPYRIGHT DISCLAIMER TRADEMARK NOTICES PART NUMBER REVISION HISTORY CONTACTING TANDBERG DATA CORPORATION
VXA-320 (VXA-3) SCSI Reference COPYRIGHT DISCLAIMER TRADEMARK NOTICES Copyright 2008 by Tandberg Data Corporation. All rights reserved. This item and the information contained herein are the property of
04-172r1 SAS-2 More counters 11 September 2005
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 September 2005 Subject: 04-172r1 SAS-2 More ers Revision history Revision 0 (21 June 2004) First revision Revision 1 (11 September
9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries
To: T10 Technical Committee From: Chris Martin (chris.martin@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 9 January 2007 Subject: 07-027r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries
16 July r1 SAS-2 Add device slot numbering fields to DISCOVER
16 July 2008 08-183r1 SAS-2 Add device slot numbering fields to DISCOVER To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 July 2008 Subject: 08-183r1 SAS-2 Add device slot numbering
Subject SMC-3 TapeAlert enhancements
To INCITS T10 Committee From Michael Banther, HP Subject SMC-3 TapeAlert enhancements Date 10 September 2006 Revision History Background Revision 0 Initial document The TapeAlert feature suffers from several
Add the following section to REPORT SUPPORTED OPERATION CODES command.
Page 1 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 To: INCITS Technical Committee T10 From: Kevin Butt, IBM Date: November 8, 2006 12:48 pm Document: T10/05-284r4 Subject: SPC-4: Self
IBM System Storage TS3310 Tape Library. Reference GA
IBM System Storage TS3310 Tape Library SCSI Reference GA32-0476-00 IBM System Storage TS3310 Tape Library SCSI Reference GA32-0476-00 Note Before using this information and the product it supports, read
Related Documents r1 SCSI Management Server Commands (MSC) Project Proposal Others as needed
To: T10 Technical Committee From: Robert Griswold, Crossroads Systems, Inc. (rgriswold@crossroads.com) Date: January 10, 2002 Subject: MSC Management commands proposal Revision History Revision 0 (January
3 2 Parameters and states for managing asymmetrical access to SCSI logical units
T10/00 232 r2 To: John Lohmeyer, chairperson, T10 From: Ken Moe Email: kenneth.moe@sun.com Date: October 20, 2000 Subject: Asymmetrical SCSI behavior 1 Introduction A significant number of SCSI storage
Item 2) In clause PL_OC2:Overall_Control state frame transmission cancellations: change the text to be as follows:
a Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: T10 SAS Protocol Working Group Contact: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 23 February 2004 Subject:
TLS-5000 TLS-6000 TLS-8000 SCSI-2 Interface Manual
The Tape Library Experts TM TLS-5000 TLS-6000 TLS-8000 SCSI-2 Interface Manual 501205 Rev. C Copyright Notice Copyright 2003 by Qualstar Corporation All Rights Reserved Information contained in this document
All page numbers refer to the printed page number, not the PDF page number.
SPI-3 Revision 10 Letter Ballot Comments 28 October 1999 by Rob Elliott, Compaq Computer Corporation All page numbers refer to the printed page number, not the PDF page number. The first three comments
Null second level LUN (0000h) (LSB) Null third level LUN (0000h) Null fourth level LUN (0000h)
Date: October 10, 2005 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Addressing more than 16384 logical units 1 Overview There are storage subsystems that are exceeding the
ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman)
To: INCITS T10 Membership From: Paul Entzel, Quantum Date: 11 November 2002 Document: T10/02-329r2 Subject: Proposed frame format for ADT 1 Related Documents T10/02-233r0 T10/02-274r0 ADT Frame Format
06-037r0 SAS-2 SMP Lists 9 January, 2006
To: T10 Technical Committee From: Steve Johnson, Brad Besmer, LSI Logic (sjohnson@lsil.com) Date: 9 January, 2006 Subject: 06-03r0 SAS-2 SMP Lists Revision history Revision 0 (8 January, 2006) First revision
04-374r0 SES-2 Define a SAS Expander element 7 November 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 7 November 2004 Subject: 04-374r0 SES-2 Define a SAS Expander element Revision history Revision 0 (7 November 2004) First revision
03-351r1 SAM-3 SPC-3 Task Attributes VPD page 11 December 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 December 2003 Subject: 03-351r1 SAM-3 SPC-3 Task Attributes VPD page Revision history Revision 0 (14 October 2003) First revision
03-344r2 SPC-3 SAM-3 Report all initiator and target ports 30 December 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 0 December 200 Subject: 0-44r2 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First
1 Overview. T10/ revision 8
Date: October 20, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: End-to-End Data Protection 1 Overview Any inconsistencies between this section and the remaining sections in the
1) Revision history 2) Related documents 3) Overview
To: INCITS Technical Committee T10 From: Fred Knight, Network Appliance Email: knight@netapp.com Date: Sept 5, 2008 Subject: SBC-3 Thin Provisioning Commands 1) Revision history Revision 0 (July 7, 2008)
04-374r2 SES-2 Define a SAS Expander element 13 January 2005
To: T0 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 3 January 2005 Subject: 04-374r2 SES-2 Define a SAS Expander element Revision history Revision 0 (7 November 2004) First revision
4.3 The Command Descriptor Block (CDB)
Date: 1 August 2000 To: T10 Technical Committee From: Ralph O. Weber Subject: CDB Structure Rewrite Several SPC-2 letter ballot comments suggest non-substantive rewriting the subclauses in clause that
1 Overview. T10/ revision 6
Date: October 07, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: End-to-End Data Protection 1 Overview Any inconsistencies between this section and the remaining sections in the
03-344r4 SPC-3 SAM-3 Report all initiator and target ports 9 February 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 9 February 2004 Subject: 0-44r4 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First
8 January r3 SAS-2 More counters
8 January 2006 04-172r3 SAS-2 More ers To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 8 January 2006 Subject: 04-172r3 SAS-2 More ers Revision history Revision 0 (21 June 2004)
Subject Report Element Information
memorandum To INCITS T10 Committee From Curtis Ballard, HP Michael Banther, HP Subject Report Element Information T10/08-066r2 Date 7 March, 2008 Revision History for original document number 06-272 Revision
6 May 2008 T10/08-018r3
To: T10 Technical Committee From: Mark Overby, NVIDIA Corporation (moverby@nvidia.com) Date: 6 May 2008 Subject: T10/08-018r3 SAT-2: NV Cache Translation Revision History Revision 0 - Initial draft of
SCSI is often the best choice of bus for high-specification systems. It has many advantages over IDE, these include:
13 SCSI 13.1 Introduction SCSI is often the best choice of bus for high-specification systems. It has many advantages over IDE, these include: A single bus system for up to seven connected devices. It
The number in square brackets at the end of each comment description counts all the comments presented in this document.
ENDL TEXAS Date: 15 January 2005 To: T10 Technical Committee From: Ralph O. Weber Subject: Response to T10 Letter Ballot comments on SPC-3 This document contains the responses to the T10 Letter Ballot
draft standard for an American National Standard for information systems - Revision 10 SCSI-3 Primary Commands 23 July 1996
draft standard for an X3T10 American National Standard 995D for information systems - Revision 10 SCSI-3 Primary Commands 23 July 1996 Secretariat: Information Technology Industry Council Notice: This
T10/01-134r Page 1 of 13
To: T10 Technical Committee From: Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: 18 July 2001 Subject: SAM-2, SPC-3, SPI-4, SBC-2 WAKEUP and reset cleanup T10/01-134r2 Revision
Assignments for Trusted Computing Group
Revision History: 0: Initial revision 1: Corrected names of DMA command versions To: T13 Technical Committee From: Jim Hatfield Seagate Technology (for the Trusted Computed Group www.trustedcomputinggroup.org
Here are the updated comments as revised at the SCSI working group meeting.
Subject: Comments on the Committee Draft 14776-381 -Small Computer System Interface -Part 381: Optical Memory Card Device Commands (SCSI OMC). 99-107R0 on T10 site. Here are the updated comments as revised
03-388r0 SBC-2 Nonvolatile caches 11 December 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 December 2003 Subject: 03-388r0 SBC-2 Nonvolatile caches Revision history Revision 0 (11 December 2003) First revision Related
TO: FROM: DATE: SUBJECT: Revisions General 2.1 The Mismatch does
TO: FROM: T10 Membership Paul A Suhler, Quantum Corporation David Black, EMC DATE: 22 October 2008 SUBJECT: T10/08-46r1, SPC-4: Correction to IKEv2-SCSI Certificate Request Payload 1 Revisions 0 Initial
03-364r1 MSC Report Bridge Mapping command 27 February 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 2004 Subject: 03-364r1 MSC Report Bridge Mapping command Revision history Revision 0 (23 October 2003) First revision
Hard Drive Self-tests
T10/99-179 rev 1 To: T10 Technical committee From: Mark Evans Quantum Corporation 500 McCarthy Boulevard Milpitas, CA USA 95035 Phone: 408-894-4019 Fax: 408-952-3620 Email: mark.evans@quantum.com Date:
Subject Report Volume Information. This command is a companion to , Report Element Information. Full background is available in that proposal.
memorandum To INCITS T0 Committee From Curtis Ballard, HP Subject Report Volume Information T0/0-2r3 DRAFT Date May, 200 Revision History Revision 0 Initial document Related Documents smc3r04 SCSI Media
03-347r0 SES-2 Reporting peer enclosure service processes 15 October 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 15 October 2003 Subject: 03-347r0 SES-2 Reing peer enclosure service processes Revision history Revision 0 (15 October 2003) First
IBM System Storage TS3100 Tape Library and TS3200 Tape Library. Reference. Machine Type 3573 GA
IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference Machine Type 3573 GA32-0547-01 Second Edition (June 2006) This edition applies to the IBM System Storage TM TS3100 Tape Library
Subject Report Element Information
memorandum T10/08-066r87 To INCITS T10 Committee From Curtis Ballard, HP Subject Report Element Information Date 8 April1 May, 2009 Revision History Revision History for original document number 06-272
500 disc CD-ROM Changer DRM-5004x series Changer Mechanism Controller SCSI Specifications
500 disc CD-ROM Changer DRM-5004x series Changer Mechanism Controller SCSI Specifications OBU0091 A June 13,1994 Pioneer Electronic Corporation Printing History Revision Date Page Descriptions A 6/13/1994
MAA3182SC, MAB3091SC INTELLIGENT DISK DRIVES OEM MANUAL
MAA3182SC, MAB3091SC INTELLIGENT DISK DRIVES OEM MANUAL SCSI LOGICAL INTERFACE SPECIFICATIONS C141-E039-01EN FOR SAFE OPERATION Handling of This manual This manual contains important information for using
To: Membership of X3T10 From: R. Reisch/R. Roberts Subject: Minutes of X3T10 MMC II Working Group - May 6 and 7, 1997
Accredited Standards Committee * X3, Information Processing Systems Doc. No. X3T10/97-190R0 Date: May 8, 1997 Project: X3T10-1228D Ref. Doc.: X3T10/94-057 Reply to: R. Roberts To: Membership of X3T10 From:
ENDL TEXAS. T10/03-005r0
ENDL TEXAS Date: 5 January 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Almost since I started editing SAM I have wanted to move anything not directly part of the architecture from SAM
04-218r1 SAT SPC-3 INQUIRY contents 29 July 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 29 July 200 Subject: 0-218r1 SAT SPC-3 INQUIRY contents Revision history Revision 0 (8 July 200) First revision Revision 1 (29 July
Software Developer's Manual
Software Developer's Manual Raster Command Reference QL-800/810W/820NWB Version 1.00 The Brother logo is a registered trademark of Brother Industries, Ltd. Brother is a registered trademark of Brother
Document T10/ rev. 1
To: T10 Committee From: Gerry Houlder, Seagate Technology, gerry_houlder@seagate.com Developed for Trusted Computing Group, www.trustedcomputinggroup.org Subj: SPC-3 Security Commands proposal Date: June
Revision History Revision 0 (T10/06-225r0): Posted to the T10 web site on 4 May 2006.
To: INCITS T10 Committee From: Matt Ball, Quantum Corporation Date: March 13, 2007 Subject: SSC-3: Key Entry using Encapsulating Security Payload (ESP) Revision History Revision 0 (T10/06-225r0): Posted
Table 180 REPORT GENERAL request. Byte\Bit SMP FRAME TYPE (40h) 4 (MSB) CRC (LSB)
Date: February 26, 2007 To: T10 Committee From Brad Besmer, LSI Logic Subject: SAS-2 SES-2 Enclosure connector information Overview An enclosure may contain multiple expanders. If one (or more) of the
Proposal For A General Purpose Logging Feature Set
T13/E00138R0 Proposal For A General Purpose Logging Feature Set To: T13 Technical committee From: Matt Rooke Fujitsu Computer Products of America 2904 Orchard Parkway San Jose, CA 95134 Phone: 408-894-3826
Revision History Revision 0 (09 December 2007) first revision
To: T10 Technical Committee From: Jeff Wolford, HP (jeff.wolford@hp.com) Date: 09 December 2007 Subject: T10/08-019r0 SAT-2 WRITE BUFFER MODE 7 to DOWNLOAD MICROCODE Mode 3 Revision History Revision 0
Unless otherwise indicated additions are shown in blue, deletions in red strikethrough, and comments in green.
ENDL TEXAS Date: 17 January 2008 To: T10 Technical Committee From: Ralph O. Weber Subject: SA Creation corrections and clarifications Introduction Revision History r0 r1 r2 r3 Initial revision Insert correct
Revision History Related Documents Overview 1. iscsi port names and device names Suggestion 2. iscsi logical unit names Suggestion
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 12 March 2003 Subject: T10/02-419r2 SAM-3 SPC-3 SAS FCP-3 SRP-2 Device identifiers and VPD data Revision History Revision 0 (2 November
CONTENTS ISO/IEC:2005(E)
2 14776-351 ISO/IEC:2005(E) CONTENTS FOREWORD... 5 INTRODUCTION... 6 1 Scope... 8 2 Normative References... 8 3 Definitions, symbols and abbreviations... 8 3.1 Definitions... 8 3.2 Symbols and abbreviations...13
Information on IEEE company IDs may be found at
To: T0 Technical Committee From: Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: March 00 Subject: SPC-3 VPD Page 83 Device Identifier rewrite Revision History Revision 0: (
T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006
T10/06-119r0 SAS-2 _REPLY 28 February 2006 To: T10 Technical Committee From: Timothy Hoglund, LSI Logic Date: 28 February 2006 Subject: Serial Attached SCSI - 2 (SAS-2) Revision History Revision 0 (28
4.1 Zoning model Zone Model Overview. T10/05-144r0 SAS-2 zoning
To: From: T10 Technical Committee Heng Liao, PMC-Sierra (heng.liao@pmc-sierra.com), Steve Gorshe, PMC Sierra (steve_gorshe@pmc.com) and Tom Grieff, HP (thomas.grieff@hp.com) Date: 19 April 2005 Subject:
Table 1 - Medium partition page(1)
To: From: Membership of X3T10 Edward Lappin Exabyte Corporation tedl@exabyte.com Date: January 23, 1995 Subject: Medium Partition Page(1-4) enhancements for SCSI-3. 1.1.1.1 Medium partition page(1) The
4 July r1 SAS-2 Enable and disable zoning
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 4 July 2006 Subject: 06-281r1 SAS-2 Enable and disable zoning Revision history Revision 0 (15 June 2006) First revision Revision
Information technology - Small Computer System Interface Part: 326 Reduced Block Commands (RBC), 2 nd Edition
FCD: 14776-326 Information technology - Small Computer System Interface Part: 326 Reduced Block Commands (RBC), 2 nd Edition Technologies de l information Interface small computer system Partie 326: (RBC)
Gene Milligab, T10 Principal member
X3T10/97-225r20 Seagate Technology Tel: 405-324-3070 10323 West Reno (West Dock) Fax: 405-324-3794 Oklahoma City, OK 73127-9705 gene_milligan@notes.seagate.com P.O. Box 12313 Oklahoma City, OK 73157-2313
Specific Changes Change 1 [modify abstract]: On the ANSI title page, remove the following paragraph from the abstract:
ENDL TEXAS Date: 5 January 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Remove AEN from SPC-3 In November, T10 agreed to remove AER (Asynchronous Event Reporting) from SAM-3. This proposal
06-378r0: SAT - Miscellaneous changes 18 August 2006
To: T10 Technical Committee From: Bob Sheffield(robert.l.sheffield@intel.com) Date: 18 August 2006 Subject: 06-378r0: SAT - Miscellaneous changes Revision history Revision 0 (18 August 2006) First revision
Block Data is the data transferred to or from the device using SCT Command Transport feature set capabilities.
1. Add the following terms to the glossary: 3.1.x Block Data Block Data is the data transferred to or from the device using SCT Command Transport feature set capabilities. 3.1.x SCT command SCT commands
INTERNATIONAL STANDARD
INTERNATIONAL STANDARD ISO/IEC 14776-113 First edition 2002-08 Information technology Small computer system interface (SCSI) Part 113: Parallel Interface-3 (SPI-3) Reference number ISO/IEC 14776-113:2002(E)
Software Developer's Manual
Software Developer's Manual Raster Command Reference TD-2020/2120N/2130N Version 1.0 The Brother logo is a registered trademark of Brother Industries, Ltd. Brother is a registered trademark of Brother
04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY 5 March 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 March 2004 Subject: 04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY Revision history Revision 0 (5 March
Proposal for Parallel SCSI: Domain Validation
T10/98-176r21 Proposal for Parallel SCSI: Domain Validation To: T10 Technical committee From: Jim McGrath Quantum Corporation 500 McCarthy Boulevard Milpitas, CA USA 95035 Phone: 408-894-4504 Fax: 408-952-3620
The number in square brackets at the end of each comment description counts all the comments presented in this document.
ENDL TEXAS Date: 4 May 2005 To: T10 Technical Committee From: Ralph O. Weber Subject: Response to T10 Letter Ballot comments on SPC-3 This document contains the responses to the T10 Letter Ballot comments
Mode/ Log/ VPD Pages For Describing Solid State Storage (Revision 3.0 Draft 4)
Mode/ Log/ VPD Pages For Describing Solid State Storage (Revision 3.0 Draft 4) Martin R. Furuhjelm Pat LaVarre Contents A. Scope B. Conventions C. Solid State Storage mode page D. Solid State Storage log
Direct Print Protocol Specification
TA Document 1998008 Direct Print Protocol Specification Version 1.0 September 15, 1998 Sponsored by: Digital Still Image Working Group of 1394 Trade Association Approved for Released by: 1394 Trade Association
MIDI CPU Firmware V User Manual
MIDI CPU Firmware V..2 MIDI CPU Firmware Version.2 User Manual Updated 23-5-3 Additional documentation available at: http://highlyliquid.com/support/ 23 Sonarcana LLC Page / 55 MIDI CPU Firmware V..2 Table
Revisions. Introduction. Proposal
To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Wednesday, January 23, 2008 10:01 am Document: T10/08-025r3 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December
Revision History Revision 0 (2 November 2002) first revision Revision 1 (31 December 2002) incorporated comments from November CAP WG.
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 31 December 2002 Subject: T10/02-419r1 SAM-3 SPC-3 SAS FCP-3 SRP-2 Device identifiers and VPD data Revision History Revision 0 (2
03-388r2 SPC-3 SBC-2 Nonvolatile caches 10 March 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 10 March 2004 Subject: 03-388r2 SPC-3 SBC-2 Nonvolatile caches Revision history Revision 0 (11 December 2003) First revision Revision
04-075r0 SBC-2 Obsolete more features 27 February 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 200 Subject: 0-075r0 SBC-2 Obsolete more features Revision history Revision 0 (27 February 200) First revision Related
Software Developer's Manual
Software Developer's Manual Raster Command Reference RJ-4250WB/4230B/3050/3150/2030/2050/2140/2150 Version 1.03 The Brother logo is a registered trademark of Brother Industries, Ltd. Brother is a registered
1.4 Revision history Revision 0 (July 7, 2008) First revision
To: INCITS Technical Committee T10 From: Fred Knight, Network Appliance Email: knight@netapp.com Date: July 7, 2008 Subject: SBC-3 Thin Provisioning Commands 1.4 Revision history Revision 0 (July 7, 2008)
INTELLIS. Modbus Direct Network Monitor
INTELLIS Modbus Direct Network Monitor System Installation and Operation Manual Phone: (201) 794-7650 Fax: (201)794-0913 Chapter 1 Modbus Protocol Revision History Revision 1.0 30 April, 2002 Initial Version
Suggested Changes. Add to Clause 8 8.AA SECURITY PROTOCOL IN command 8.BB SECURITY PROTOCOL OUT command. Jim Hatfield (Seagate) Page 1 of 5
To: T10 Technical Committee From: Jim Hatfield, Seagate (James.C.Hatfield@seagate.com) Date: May 8, 2007 Subject: Revision History Revision 0 (Feb. 14, 2007) First revision Revision 1 (Mar. 1, 2007) Incorporate
2 May r2 SAS-2 WWN-based Attached Device Name for SATA
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 May 2007 Subject: 06-476r2 SAS-2 WWN-based Attached Device Name for SATA Revision history Revision 0 (31 October 2006) First revision
Proposal for Storage and Access of Data on Auxiliary Memory
Proposal for Storage and Access of Data on Auxiliary Memory Revision History Author: Sid Crighton Phone: +44 117 3128339 Location: R&D, Hewlett-Packard Ltd, Bristol, UK Email: ianc@bri.hp.com Version Date
Revisions. Introduction. Proposal
To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Monday, January 07, 2008 6:31 pm Document: T10/08-025r1 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December