From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make ide-probe more robust to non-ready devices
Date: 05 Jan 2003 00:03:02 -0700 [thread overview]
Message-ID: <m1adigjcyh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1041713307.2036.10.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sat, 2003-01-04 at 09:34, Benjamin Herrenschmidt wrote:
> > I don't expect this patch to break any existing working configuration,
> > so please send to Linus for 2.5. If you accept it, I'll then send a 2.4
> > version to Marcelo as well. This have been around for some time and,
> > imho, should really get in now.
>
> There is a ton of stuff pending for 2.5 IDE. Unfortunately 2.5 isn't in
> a state I can do any usable testing so it will have to wait. The Marcelo
> 2.4 tree is current and I'm doing the work in 2.4 first now.
>
> Rusty seems to have a lot of the module stuff in hand so hopefully I'll
> get back onto 2.5 after LCA
Whatever the kernel is let me send a hearty me to on this one. I have
been doing something similar without problems.
I have heard reports that there are some drive/controller combinations
that polling the BSY bit does not work on to get them past the initial
drive spin up state. However waiting for BSY to clear is no worse
than anything else on those setups, and this works for quite a few.
Eric
next prev parent reply other threads:[~2003-01-05 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 9:34 [PATCH] Make ide-probe more robust to non-ready devices Benjamin Herrenschmidt
2003-01-04 9:41 ` Benjamin Herrenschmidt
2003-01-04 9:53 ` Benjamin Herrenschmidt
2003-01-04 20:48 ` Alan Cox
2003-01-05 7:03 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 8:49 Benjamin Herrenschmidt
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=m1adigjcyh.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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