From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org, hancockr@shaw.ca
Cc: linux-ide@vger.kernel.org
Subject: Re: [patch 29/30] sata_nv: don't read shadow registers when in ADMA mode
Date: Fri, 09 Mar 2007 07:35:52 -0500 [thread overview]
Message-ID: <45F154A8.1050606@garzik.org> (raw)
In-Reply-To: <200703061038.l26AcD3M019553@shell0.pdx.osdl.net>
akpm@linux-foundation.org wrote:
> From: Robert Hancock <hancockr@shaw.ca>
>
> Reading from the ATA shadow registers while we are in ADMA mode may cause
> undefined behavior. Don't read the ATA status register when completing
> commands for this reason, it shouldn't be needed as the controller will
> notify us if the command failed. Also, don't allow commands with result
> taskfile requested to execute in ADMA mode, since that requires accessing
> the shadow registers. We also still need to override tf_read since libata
> will read the result taskfile on a command failure, and we need to go into
> port register mode before allowing this.
>
> Signed-off-by: Robert Hancock <hancockr@shaw.ca>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/ata/sata_nv.c | 33 ++++++++++++++++++++-------------
> 1 file changed, 20 insertions(+), 13 deletions(-)
Robert, do you think this should be pushed into #upstream-fixes (2.6.21-rc)?
I lean towards "yes", since it is a needed-by-hardware fix, but I also
am interested in testing feedback since it is so late in the 2.6.21-rc game.
Jeff
next prev parent reply other threads:[~2007-03-09 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:38 [patch 29/30] sata_nv: don't read shadow registers when in ADMA mode akpm
2007-03-09 12:35 ` Jeff Garzik [this message]
2007-03-09 14:27 ` Robert Hancock
2007-03-09 15:39 ` Alistair John Strachan
2007-03-09 22:54 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F154A8.1050606@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.