This message is from the T13 list server.
Consider creating an ATA pass-through mechanism for standard commands and a separate ATA pass-through for vendor unique commands. ... For standard defined ATA commands each field has a well-defined set of values or is not applicable.
Help, I don't exactly understand.
I do like the idea of tuning the design for the fast path of device and host likely in agreement over how many bytes to copy which way and in agreement that those bytes make up a series of whole 0.5 KiB blocks.
But pass thru of more than was standard is pass thru of newly standard and vendor-specific, not just pass thru of vendor-specific. That is, an old device thinks that any newly standard command is reserved, obsolete, or vendor-specific.
Tell me again how the new device benefits by the new host saying the passed thru command is now standard?
Pat LaVarre
