Incompatibility between SES-2 r11 and r10?

Fairchild, Steve steve.fairchild at hp.com
Thu Apr 14 11:08:02 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Fairchild, Steve" <steve.fairchild at hp.com>
*
Kevin/Rob,

Please leave the INVALID bit as defined in r11.  Changing the sense of that at this point would cause problems.

Thanks,

Steven Fairchild
Senior Member Technical Staff
Hewlett-Packard Corporation
MS150901
20555 SH 249
Houston, TX 77070
281 514 6448
steve.fairchild at hp.com




-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org]On Behalf Of
Kevin_Marks at Dell.com
Sent: Thursday, April 14, 2005 10:39 AM
To: Elliott, Robert (Server Storage); dougg at torque.net; t10 at t10.org
Cc: Chris_Fore at adaptec.com
Subject: RE: Incompatibility between SES-2 r11 and r10? 


* From the T10 Reflector (t10 at t10.org), posted by:
* <Kevin_Marks at Dell.com>
*
Rob,

If we defined bit 4 byte 0 to indicate r11+ format, I would have no
problem changing the INVALID bit back to a VALID.

Kevin


Kevin Marks (Kevin_Marks at dell.com)
Storage Architecture 
-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Elliott,
Robert (Server Storage)
Sent: Wednesday, April 13, 2005 3:18 PM
To: dougg at torque.net; t10 at t10.org
Cc: Chris_Fore at adaptec.com
Subject: RE: Incompatibility between SES-2 r11 and r10? 

* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <elliott at hp.com>
*
We could define bit 4 byte 0 set to one means the structure follows the
r11+ format.

---
Rob Elliott, HP Server Storage
elliott at hp.com  

> -----Original Message-----
> From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf 
> Of Douglas Gilbert
> Sent: Tuesday, April 12, 2005 4:01 PM
> To: t10 at t10.org
> Cc: Chris_Fore at adaptec.com
> Subject: Re: Incompatibility between SES-2 r11 and r10? 
> 
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Douglas Gilbert <dougg at torque.net>
> *
> Yes, I also noticed major differences in the SES-2
> Additional Element Status diagnostic page between
> r11 and r10.
> 
> Currently there is only one SES-2 version descriptor:
> 3e0h "SES-2 (no version claimed)" [ref: spc3r22a.pdf
> Table D.14]. Perhaps more SES-2 version descriptors
> could be added. of course, version descriptors are futile
> unless target firmware supports them (in the response
> of a standard INQUIRY).
> 
> Another approach would be to use a version field like MMC
> features.
> 
> Doug Gilbert
> 
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
> 
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org





More information about the T10 mailing list