Further updates to timestamps (T10/13-133)

Paul Suhler Paul.Suhler at quantum.com
Tue May 7 10:53:28 PDT 2013


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1305070_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1305070_image001.gif">image001.gif</a>

Hi, Ralph.
In line with the decision to use the term "device clock," there are a couple
of changes needed in subclause 6.46 SET TIMESTAMP command, which the current
revision of the proposal shows as having no changes:
The SET TIMESTAMP command (see table 331) requests that the device server
initialize the timestamp device clock (see 5.2), if the SCSIP bit is set to
one or the TCMOS bit is set to one in the Control Extension mode page (see
7.5.9). If the SCSIP bit is set to zero, the SET TIMESTAMP command shall be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB. This
command uses the MAINTENANCE OUT CDB format (see 4.2.2.3.4).
<<No changes to Table 331. >>
The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in
table 331 for the SET TIMESTAMP command.
The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in
table 331 for the SET TIMESTAMP command.
The PARAMETER LIST LENGTH field specifies the length in bytes of the SET
TIMESTAMP parameters that shall be transferred from the application client to
the device server. A parameter list length of zero specifies that no data
shall be transferred, and that no change shall be made to the timestamp
device clock.
The CONTROL byte is defined in SAM-5.
Thanks,
Paul
_____________________________________________________________________________
________________________
Paul A. Suhler, PhD | Firmware Engineer | Quantum Corporation | Office:
949.856.7748 | paul.suhler at quantum.com
[be-certain_lockup.gif]<http://www.quantum.com/&gt;



More information about the T10 mailing list