This message is from the T13 list server.
In reading the proposal, it seems that there is a issue. Enough so the write a proposal. If the state does occur as the proposal describes, then the bad data is read to clear the DRQ. A performance issue and as you comment, issue a soft reset and re-issue the command. How long does a soft reset take (performance hit). > From: Hale Landis <[EMAIL PROTECTED]> > Reply-To: Hale Landis <[EMAIL PROTECTED]> > Date: Mon, 15 Nov 2004 10:57:01 -0700 > To: "[EMAIL PROTECTED]" <[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 *** > > >
