This message is from the T13 list server.
Just as a point of reference - - - here is the last proposal revision:
http://t13.org/docs2002/e01141r2.pdf
Thank You !!!
-----------------------------------------------------------------
Jim Hatfield
ATA Interface Firmware & T13 (ATA/ATAPI) Standards Representative
Seagate Technology - PSG
e-mail: [EMAIL PROTECTED]
s-mail: 389 Disc Drive; Longmont, CO 80503 USA
voice: 720-684-2120
fax : 720-684-2711
====================================================
|---------+---------------------------->
| | "Hale Landis" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | rg |
| | No Phone Info |
| | Available |
| | |
| | 06/16/2003 08:46 |
| | AM |
| | Please respond to|
| | "Hale Landis" |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: "T13 List Server" <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Re: [t13] ATA-7 Write DMA Queued FUA EXT problem
|
>------------------------------------------------------------------------------------------------------------------------------|
This message is from the T13 list server.
Does FUA mean access the media ONLY for the single command that
requests FUA or for all data currently in the "write cache"
(basically combining the effect of some writes followed by a FLUSH
CACHE) or is it something far more complex (and therefore more
subject to failure?).
Did the requester of this "feature" ever provide more info or a
better description of what it was they really wanted?
Hale
*** Hale Landis *** www.ata-atapi.com ***
