From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] libata-sff: Correct use of check_status()
Date: Mon, 22 Oct 2007 14:36:25 -0400 [thread overview]
Message-ID: <471CEDA9.30001@garzik.org> (raw)
In-Reply-To: <20071022114056.78bafbf1@the-village.bc.nu>
Alan Cox wrote:
>>> + tf->command = ata_chk_status(ap);
>>> tf->feature = ioread8(ioaddr->error_addr);
>>> tf->nsect = ioread8(ioaddr->nsect_addr);
>>> tf->lbal = ioread8(ioaddr->lbal_addr);
>> applied, with a sigh: it's in SFF, so I saw nothing wrong with
>> ata_check_status(). I checked -- no SFF driver overrides it according
>> to my audit, therefore the previous version was faster while still correct.
>
> I hit it with the NS87415 where ata_check_status() doesn't do the right
> thing. Later on it turned out that there were enough other bugs when
> enabling DMA that it needed its own tf read method anyway.
>
> Alternative is to go through and clear up chk_atatus v check_status
> (rename one sff_ to be clear), and explicitly document the assumption in
> tf_read. That way it'll be obvious to whoever hits it in future and they
> can supply their own tf_read method.
>
> Preferences ?
That was my general preference -- use your own ->tf_read()
Jeff
prev parent reply other threads:[~2007-10-22 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:25 [PATCH] libata-sff: Correct use of check_status() Alan Cox
2007-10-18 0:58 ` Jeff Garzik
2007-10-22 10:40 ` Alan Cox
2007-10-22 18:36 ` Jeff Garzik [this message]
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=471CEDA9.30001@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).