This message is from the T13 list server.
Except for SEEK (which is a new item) all the other obsolete commands were made obsolete at least 5 years ago. So the host community has had plenty of notice to NOT rely on them going forward. Certainly it's reasonable to assume that the committee would not extend obsolete commands that people were told not to rely on over 5 years ago into the new addressing space? Afterall, the promise made to other people was that you did not have to worry about doing new stuff for obsolete commands. SEEK is an exception of course, and deserves independent discussion. Since it was not obsolete yet, extending it to the new addressing might make sense - or might not. Whichever is decided, I'd still advocate making it obsolete soon so that at least in another 5 years we can hopefully forget about it forever. Jim -----Original Message----- From: Pat LaVarre [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 7:32 AM To: [EMAIL PROTECTED] Subject: [t13] vendor-specific as good as optional, outside the o.s.? This message is from the T13 list server. >>> Hale Landis 03/20/02 05:47PM >>> > ... R/W Long commands ... > You must remember that if no OS > uses the command, the command > is likely to disappear over time. Agreed. Fun to see commodity desktop hosts as shipped using elements of Scsi that never appeared in Ata, like Scsi op x04 Format. > I think most people thought then > (and continue to think) that this functionality, > if supported by a drive, is the reason > we have "vendor specific" commands. Hang on a minute. There is a small gap between Optional and Obsolete, but a wide wide wide gap between Optional and VendorSpecific The point of keeping Seek, Read/WriteLong, Recalibrate, etc. etc. Optional is to give device folk a chance of implementing something host folk want in advance. By quietly neglecting to carry forward these commands past the 28 and 32 bit Lba limits, T10 & T13 have in effect made it more difficult than it was for host & device folk to cooperate. I'd think the host folk will scream first: they face the prospect of getting locked into a single source for the vendor-specific commands they need. Among the host folk, maybe the bridge whatever-to-Ata folk should scream first: they can't translate T10 to T13 in the 28 to 32 bit Lba range i.e. not above 128GiB @ 0.5KiB/block. x4402 Pat LaVarre [EMAIL PROTECTED] http://members.aol.com/plscsi/ >>> McGrath, Jim 03/20/02 06:33PM >>> > The people on T13, > particularly the officers and editors, > work quite long and hard > and produce something > of substantial value to the industry. Yes certainly. This fact should Not be in dispute, decidely I hope it is Not.
