From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
bugsbuggy@ymail.com
Subject: Re: [PATCH #upstream-fixes] libata: set NODEV_HINT for 0x7f status
Date: Mon, 26 Jan 2009 06:39:59 -0500 [thread overview]
Message-ID: <497DA10F.6020507@garzik.org> (raw)
In-Reply-To: <497BBFA8.4080804@kernel.org>
Tejun Heo wrote:
> Asus Pundit-R with atiixp controller has the second port missing and,
> very unusually, its status is stuck at 0x7f and all others at 0. This
> meanst that it fails TF access test but gets detected as a disk due to
> classification code check and then evades polling IDENTIFY presence
> detection thanks to the missing BSY in the status value causing
> excessive delays during boot.
>
> This patch makes libata-sff HSM set NODEV_HINT if the status is 0x7f
> to make polling IDENTIFY presence detection work for these machines.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> drivers/ata/libata-sff.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
applied
prev parent reply other threads:[~2009-01-26 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 1:26 [PATCH #upstream-fixes] libata: set NODEV_HINT for 0x7f status Tejun Heo
2009-01-26 11:39 ` 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=497DA10F.6020507@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugsbuggy@ymail.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).