[MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No Event'
daviburg at windows.microsoft.com
Wed Apr 1 14:51:57 PDT 2009
* From the T10 Reflector (t10 at t10.org), posted by:
* David Burg <daviburg at windows.microsoft.com>
I'd rather see NEA clarify that have the host benchmark a device before it
may know how to use it. Spec needs to be clarified.
From: owner-mtfuji5 at avc-pioneer.com [mailto:owner-mtfuji5 at avc-pioneer.com] On
Behalf Of keiji_katata at post.pioneer.co.jp
Sent: Monday, March 30, 2009 9:42 PM
To: mtfuji5 at avc-pioneer.com
Cc: T10 Reflector; Ope Aladekomo
Subject: Re: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No
Hi david and Mike,
* Immed bit
Fuji spec says that if this bit is set to 0 and the device does not support
queuing the command shall be terminated as Check Condition. This is same with
MMC. Bill changed just name from Immed to Polled. They are same.
* the error reporting
I believe no device will report an error on Immed=0. Because Win98/ME do not
this bit to 1 any time. Some drive test system in PC/ODD venders still use
Win98, then any ODD that does not support queing will ignore this bit.
* no change event
NEA means no event is available to report. So some drive may use NEA=1 when
device has no (new) event to be reported. To detect supported Event you may
check "Supported Classes" field in Event Header. You need not use try and
* 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