From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 09:49:35 +0100 [thread overview]
Message-ID: <1041756574.642.35.camel@zion.wanadoo.fr> (raw)
On Sat, 2003-01-04 at 21:48, Alan Cox wrote:
> 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
Well, actually, I'd like to see this patch in 2.4 asap too ;) It should
apply "as is" with some offset.
As Eric W. Biederman noticed, it may not be enough for some really
broken devices, but will not harm neither on these, and will fix the
problem on a whole lot of better ones. It's definitely necessary with
some WD hard disks and the "combo" DVD/CDRW drive shipped by Apple on
some ibooks (Apple firmware typically does a reset of all drives just
before booting the kernel, without waiting)
Ben.
next reply other threads:[~2003-01-05 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 8:49 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-04 9:34 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
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=1041756574.642.35.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®