From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>,
"Andre Hedrick" <andre@linux-ide.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] IDE probe & waiting for busy
Date: Sun, 22 Sep 2002 11:48:34 +0200 [thread overview]
Message-ID: <20020922100626.18852@192.168.4.1> (raw)
>
>Ben, in fact I implemented it. :) I have been meaning to merge it into
>the 2.4-ac stuff Alan/Andre are doing.
Ok, great.
Do you actually wait for busy to go away before sending the
execute diag command ? Or do you just blast it to the device
right when entering the probe code ?
I'm concerned that if you don't wait for busy to go away, you
end up interrupting the drive reset process with execute diag.
which may not be the best thing to do...
Anyway, if you have a patch ready, pls share so I can get
that tested by the various users of those problematic
setups !
Thanks,
Ben.
next reply other threads:[~2002-09-22 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 9:48 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-21 15:28 [RFC] IDE probe & waiting for busy Benjamin Herrenschmidt
2002-09-22 4:52 ` Andre Hedrick
2002-09-22 5:01 ` Jeff Garzik
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=20020922100626.18852@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=andre@linux-ide.org \
--cc=jgarzik@mandrakesoft.com \
--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