solid state mode/ vpd/ event work

Banther, Michael michael.banther at hp.com
Mon Dec 20 03:28:44 PST 2004


* From the T10 Reflector (t10 at t10.org), posted by:
* "Banther, Michael" <michael.banther at hp.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C4E687.10921CC3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I do not understand your comment below, 'By inventing a new use for =
EVPD
....'  Do you intend to define a new VPD page to hold the 'read-only
descriptive data?'

Regards,
Michael Banther
Hewlett-Packard Ltd.
Telephone +44 (117) 312-9503


-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Pat
LaVarre
Sent: 17 December 2004 17:36
To: t10 at t10.org
Subject: solid state mode/ vpd/ event work

* From the T10 Reflector (t10 at t10.org), posted by:
* "Pat LaVarre" <plavarre at lexarmedia.com>
*
Hello again, remember Me?  We've now volunteered me to redraft the
(04-362r0.pdf from Lexar) proposal for vpd/ mode/ etc. definitions that
help the host tune its use of solid-state storage.  I hope to see ya'll
in person at the next CAP WG.

I'm working face to face with people who attended the November CAP WG,
also from the written minutes that I quote below.  For example, I plan
to begin by answering the request to divide the solid-state data into
three categories: a) rewritable settings data, b) read-only descriptive
data, and c) pollable event data.

But if I may, I'd first like to take a moment to confirm I understand
the overall approach.  I hear we the committee saying Four things:

---

1) Massively distributed hosts may choose to adopt this new standard by
beginning with the negligible risk of trying to fetch the newly =
standard
solid-state mode page, from any PDT x 0E 07 05 04 00 device.

2) With devices that do not make the new page available, the system =
will
survive as it already does when the host looks for other mode pages =
with
less than universal support, such as the code x05 HDD C:H:S page or the
x2A C/DVD media compatibility page.

3) After confirming a particular device does make the new page
available, the host may proceed to fetch the read-only descriptive data
by trying op x12 INQUIRY with the byte 1 mask x01 EVPD bit of the CDB
set.  The host may alter the rewritable settings via Mode Select, in
particular choosing to enable the new unit attention or not.  =
Thereafter
the host may poll for events.

4) By inventing a new use for EVPD and yet another form of polling, we
might break (intrinsically fragile) opaque bridge chips, but that's a
cost the device folk who wish to establish this new standard can agree
to pay before shipping a device that does make the new page available.

---

Is that our thinking?

Thanks in advance, hope this helps, Pat LaVarre
http://www.t10.org/ftp/t10/members.txt

--- Background ---

http://t10.org

http://t10.org/t10_mins.htm

04-367r1 Minutes of CAP Working Group - Nov 9-10, 2004
http://www.t10.org/ftp/t10/document.04/04-367r1.htm

5.3.3  SBC-2: Proposal for USB Solid State Drive Mode Sense
specification (04-362r0) [Furuhjelm]
ftp://ftp.t10.org/t10/document.04/04-362r0.pdf

Steffen Hellmold presented a proposal for defining a mode page for USB
solid-state drives (04-362r0). The group recommended using a VPD page
instead of a mode page for most of the proposed data, as well as other
changes in the proposal.

George Penokie noted that the proposal contains three types data:


o      Unchangeable data that can be represented in a VPD page

o      Data that the host wants to set that can be represented in a =
Mode
page

o      Data that needs to be polled (e.g., the health indicator) which
needs to be represented by a Log page (with unit attention), polling
with Request Sense, or polling with a specialized command

Steffen agreed to prepare a revised proposal for consideration at the
next meeting.

...

---=20

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


------_=_NextPart_001_01C4E687.10921CC3
Content-Type: text/x-vcard;
	name="BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf"
Content-Transfer-Encoding: base64
Content-Description: BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf
Content-Disposition: attachment;
	filename="BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf"

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkJBTlRIRVI7TUlDSEFFTA0KRk46QkFOVEhFUixN
SUNIQUVMIChIUC1Vbml0ZWRLaW5nZG9tLGV4MikNCk9SRzpIUC1Vbml0ZWRLaW5nZG9tLGV4MjtD
NjAwLTUzMDINClRFTDtXT1JLO1ZPSUNFOjMxMi05NTAzDQpURUw7V09SSztWT0lDRTorNDQgMTE3
IDMxMiA5NTAzDQpBRFI7V09SSzo7TVMgMkIyMjs7QlJJU1RPTCwgR0INCkxBQkVMO1dPUks7RU5D
T0RJTkc9UVVPVEVELVBSSU5UQUJMRTpNUyAyQjIyPTBEPTBBQlJJU1RPTCwgR0INCkVNQUlMO1BS
RUY7SU5URVJORVQ6bWljaGFlbF9iYW50aGVyQGhwLmNvbQ0KUkVWOjIwMDMwNzE3VDA4Mjk0OFoN
CkVORDpWQ0FSRA0K

------_=_NextPart_001_01C4E687.10921CC3--




More information about the T10 mailing list