This message is from the T13 list server.
I would say that giving guidance to the host as to what to do is always a good thing. This bit gives the host guidance as to what will happen in the case of an error. It might be sufficient just to add language stating that DRQ must be 0 if ERR is 1, but that's my opinion. I know I have seen devices that do this. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hale Landis Sent: Monday, November 15, 2004 9:57 AM To: [EMAIL PROTECTED] Subject: Re: [t13] e04155r0 - DRQ=0 When ERR=1 Feature This message is from the T13 list server. On Mon, 15 Nov 2004 09:48:40 -0700, [EMAIL PROTECTED] wrote: >This message is from the T13 list server. >I have some questions about the new proposal >"e04155r0 - DRQ=0 When ERR=1 Feature and > Allocation Identify Device Words Proposal" >http://t13.org/docs2004/e041559r0-DRQ-ERR-and-ID-Words.pdf >Why do we need this ? >What problem does it really solve ? >Why should we define a feature that allows a BAD DEVICE to do something >stupid instead of fixing the bad device ? I agree entirely with Mr. Hatfield. What "problem" is this trying to solve? I've never seen BSY=0 DRQ=1 ERR=1 status be a problem. It is equivalent to BSY=0 DRQ=0 ERR=1. Either way a "well designed" host will issue a Soft Reset (SRST) and probably retry the failing command. Hale *** Hale Landis *** www.ata-atapi.com ***
