From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
linux-ide@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Takashi Iwai <tiwai@suse.de>,
marc.c.dionne@gmail.com, dl9pf@gmx.de,
bug-track@fisher-privat.net, sitsofe@yahoo.com
Subject: Re: [PATCH] Re: [git patches] libata updates - (improve post-reset device ready test) regression
Date: Fri, 09 May 2008 00:37:00 -0400 [thread overview]
Message-ID: <4823D4EC.7060407@garzik.org> (raw)
In-Reply-To: <4823BD8E.40109@gmail.com>
Tejun Heo wrote:
> This means that we need to make custom readiness tests for controllers
> using 0x77 or 0x7f. Eeeek... Both groups of controllers are behaving in
> incorrect way. Controllers shouldn't use 0x77 or 0x7f for either busy
> or ready states - it's invalid for both, yet, some use the 77/7f for
> busy while others use them for ready state. Great. :-(
I think that's assuming too much? PATA and SATA are quite different
here... in PATA the status is mostly the value from the device directly
off the wires. in SATA, it may be from the device or from the
controller. And "smart" or firmware-based controllers may generate
their own status, too, apart from the device's status.
So that results in varied status returns, and not all the time is a
definite "ready" or "not ready" obvious.
Jeff
next prev parent reply other threads:[~2008-05-09 4:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 15:48 [git patches] libata updates Jeff Garzik
2008-05-06 16:23 ` Linus Torvalds
2008-05-07 14:56 ` [git patches] libata updates - (improve post-reset device ready test) regression Markus Trippelsdorf
2008-05-07 16:35 ` Takashi Iwai
2008-05-08 3:13 ` Marc Dionne
2008-05-08 9:45 ` Jan-Simon Möller
2008-05-08 15:35 ` [PATCH] " Jeff Garzik
2008-05-08 16:05 ` Takashi Iwai
2008-05-08 16:18 ` Markus Trippelsdorf
2008-05-08 17:40 ` Alexey Fisher
2008-05-08 19:21 ` Hugh Dickins
2008-05-08 21:43 ` J.A. Magallón
2008-05-09 14:54 ` Mark Lord
2008-05-08 21:51 ` Marc Dionne
2008-05-09 2:57 ` Tejun Heo
2008-05-09 3:01 ` Tejun Heo
2008-05-09 4:27 ` Justin Mattock
2008-05-09 3:43 ` Justin Mattock
2008-05-09 4:37 ` Jeff Garzik [this message]
2008-05-10 6:34 ` Tejun Heo
2008-05-09 5:09 ` Alexey Fisher
2008-05-09 10:59 ` Marc Dionne
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=4823D4EC.7060407@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=bug-track@fisher-privat.net \
--cc=dl9pf@gmx.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.c.dionne@gmail.com \
--cc=markus@trippelsdorf.de \
--cc=sitsofe@yahoo.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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).