[MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No Event'

[Takaharu Ai]

* From the T10 Reflector (t10 at t10.org), posted by:
* Takaharu Ai <ai.takaharu at jp.panasonic.com>
*
Hello Bill, David,
I missed that sentence in the original David's message, but I think the
wording is not correct. As I explained, the existence of an event for a
Class does not affect to the NEA bit setting. NEA just indicate whether
or not the drive supports the requested event.
For example, if a drive supports Oprational Change, Power, Media and
Device Busy event Classes, and the host requests External Request only,
then the drive returns only the 4-byte Event header with NEA=1, even if
the drive has an Event for a supported Class. Another example is if the
host requests Operational Change Class and the drive does not have any
Event for that Class, the drive must report Event Header with NEA=0,
Notification Class=001b and Operational Change Class Event Descriptor
with Operational Event=0h.
So, the sentence should be "Regardless of the existence of an Event, if
none of the requested noticiation Class is supported, ..."
Best Regards,
Harry Ai
VEBU,
AVC Networks Company,
Panasonic Corporation
Osaka, Japan
---------------- Start of the original message ----------------
>From: Bill McFerrin <billmc37 at ctesc.net>
>To: keiji_katata at post.pioneer.co.jp
>Cc: mtfuji5 at avc-pioneer.com, T10 Reflector <t10 at t10.org>, Ope Aladekomo
<Ope.Aladekomo at microsoft.com>
>Date: Mon, 13 Apr 2009 10:54:25 -0500
>Subject: Re: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No
Event'
>
> Hi
> The sentence: "If no event / of the requested notification class / has
> occurred, ..." was David Burg's attempt to be clear about what he
> believes to be the meaning of the text. It is not in any version of MMC.
> Since some people are confused, clarification is needed. It appears that
> David's proposed sentence is correct.
> 
> Cheers,
> Bill McFerrin
> 
> 
> keiji_katata at post.pioneer.co.jp wrote:
> > * From the T10 Reflector (t10 at t10.org), posted by:
> > * keiji_katata at post.pioneer.co.jp
> > *
> >
> >
> > Hi Bill,
> >
> > I might misunderstand this item.
> > Bill, let me know when did you add this sentence in MMC?
> > Could you tell me the file name of the MMC meeting minutes?
> >
> > Best regards,
> >
> > Keiji Katata
> > PIONEER CORP.
> >
> >
> >
> >
> >
> > Bill McFerrin <billmc37 at ctesc.net>@avc-pioneer.com on 2009/04/08 04:14:53
> >
> > mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(B
> >
> > $BAw?.<T(B:     owner-mtfuji5 at avc-pioneer.com
> >
> >
> >
> >
> >
> >
> >
> > $B08 at h(B:  <mtfuji5 at avc-pioneer.com>
> > cc:    T10 Reflector <t10 at t10.org>, Ope Aladekomo
<Ope.Aladekomo at microsoft.com>
> > $B7oL>(B:  Re: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of
'No Event'
> >
> > * From the T10 Reflector (t10 at t10.org), posted by:
> > * Bill McFerrin <billmc37 at ctesc.net>
> > *
> > Hi,
> > Your are right: The response is incorrect. Fuji agrees.
> >
> > The more accurate wording you suggested ($B!H(BIf no event /of the
requested
> > notification class/ has occurred, $B!D!I(B) is a good thing. It might
be
> > useful to add a "for example".
> >
> > Cheers,
> > Bill
> >
> > David Burg wrote:
> >   
> >> Hello,
> >>
> >> During our testing of Windows 7, our engineers noticed a difference in
> >> the devices$B!G(B implementation of GESN command response to say the
same
> >> $B!F(Bno event$B!G(B answer. Below is a capture of an 8 bytes answer
|from one
> >> device and of an 4 bytes answer from another device.
> >>
> >> (Note that BusTrace incorrectly interpreted the Polled bit as Immed.)
> >>
> >> We believe this complies to MMC$B!G(Bs:
> >>
> >> cid:image002.jpg at 01C9AC5C.CBEA04D0
> >>
> >> (One might want to be careful to clarify $B!H(BIf no event /of the
> >> requested notification class/ has occurred, $B!D!I(B because event may
occur
> >> in another class and yet can$B!G(Bt be reported.)
> >>
> >> The other device responds:
> >>
> >> This does not seem allowed by the current spec, although it is not
> >> completely obvious.
> >>
> >> Also, some software engineers thought they would get NEA = 1b and 4
> >> bytes, based on the name of that bit $B!H(BNot Event
Available$B!I(B. >From an
> >> English language point of view, there is indeed no event available.
> >> However, the spec definition of the bit then contradicts with what one
> >> would expect out of English language alone:
> >>
> >> $B!H(BIf NEA (No Event Available) is set to one, the Drive supports
none of
> >> the requested notification classes. If NEA
> >>
> >> is set to zero, at least one of the requested notification classes is
> >> supported.$B!I(B
> >>
> >> This sounds more like $B!H(BNo Requested Class Supported$B!I(B.
> >>
> >> So, Microsoft believes this GESN section should be reviewed in detail
> >> and clarified.
> >>
> >> With regards,
> >>
> >> David.
> >>
> >>	 
> > *
> > * 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
> >
> >   
----------------- End of the original message -----------------
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org