RE: [t13] Command Format

Curtis Stevens Tue, 10 Aug 2004 12:13:23 -0700

Title: Command Format

Tony

I guess I was really unclear in my earlier E-Mail, some people made the same comment you did. The command code is currently listed as the last byte of the command structure. It is in the same place in every case. It is still searchable. It just seems a bit redundant to have the command code in 2 places in the same section.
Since the goal for the command set in now a stand alone standard, I am attempting a first pass at making the command set transport neutral. I think that there is value in listing the protocol, but the transport documents (PATA/SATA) need to define how the protocol works for their transport. This is why I think putting a paragraph on each protocol would have value, but the state transition diagrams etc belong in the transport docs.
I am still skeptical about the pre-requisites. One reason is that they are the same for the vast majority of the commands just say DRDY=1. The documentation is inconsistent because some of the commands say BSY=0, DRDY=1. I also found a command that has no prerequisite section. I think that we should state upfront that DRDY=1 is required for most commands and that deviations are in the command description.
I agree, I will move the description up and see what happens.

------------------------------------------------

Curtis E. Stevens

20511 Lake Forest Dr. #C 214-D

Lake Forest, Ca. 92630

Phone: 949-672-7933

Cell: 949-307-5050

E-Mail: [EMAIL PROTECTED]

-----Original Message-----
From: Tony Goodfellow [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 11:41 AM
To: Curtis Stevens; 'ATA (E-mail)'
Subject: RE: [t13] Command Format

For what it is worth – here are my comments.

a) Command Code – It would be a pain to have to flip back to a table – and for those of use who read these things electronically it is a good search key.

b) Protocol – It is again useful information. It needs two references, PATA,SATA.

c) Prerequisites – Again it needs two sub sections – PATA and SATA

d) Description- I have always complained that putting the description at the end of the definition is a very inconvenient place. To my mind it should be at the beginning after the Command Code. If the description is different for P{ATA and SATA then two descriptions should be given.

Tony Goodfellow

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stevens
Sent: Monday, 09 August, 2004 15:06
To: ATA (E-mail)
Subject: [t13] Command Format

This following document has been posted: http://www.t13.org/docs2004/e04139r0-Command_Format_Example.pdf This contains some sample command proposals for the new command set standard. There are also several questions about what kind of information needs to reside in this doc. Please take a look and forward me your commands. It would be good if I could get a second rev up prior to the meeting.