From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Todd Poynor <tpoynor@mvista.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tim.bird@am.sony.com, dsingleton@mvista.com
Subject: Re: [PATCH] Configure IDE probe delays
Date: Fri, 30 Jul 2004 20:54:32 -0400 [thread overview]
Message-ID: <410AEDC8.6030901@pobox.com> (raw)
In-Reply-To: <1091226922.5083.13.camel@localhost.localdomain>
Alan Cox wrote:
> On Gwe, 2004-07-30 at 20:11, Todd Poynor wrote:
>
>>IDE initialization and probing makes numerous calls to sleep for 50
>>milliseconds while waiting for the interface to return probe status and
>>such.
>
>
> Please make it taint the kernel if you do that so we can ignore all the
> bug reports. That or justify it with a cite from the ATA standards ?
The 50 milliseconds is a pragmatic number you won't find in any
standard. Linux IDE driver does the "bang at the door" method of
probing, which you won't find in any standard either :)
The ATA standard defines times for things like software reset (SRST),
but Linux IDE driver takes a unique approach -- just issue down the
first command (IDENTIFY DEVICE), and see what you get. The command (or
error) responses give you information that allows you to probe further.
The 50ms delay hides things like the device coming out of reset, the
interface powering up on the first command issued to the device, etc.
IMO the number is a "change it at your own risk" number that shouldn't
be touched unless the touch-er is also willing to rewrite the IDE
driver's probe code ;-)
SATA is much faster at probing, and PATA will become progressively less
common, so the motivation for changing the probe code is low, too.
Jeff
next prev parent reply other threads:[~2004-07-31 0:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 19:11 [PATCH] Configure IDE probe delays Todd Poynor
2004-07-30 21:36 ` Lee Revell
2004-07-30 22:35 ` Alan Cox
2004-07-31 0:12 ` Lee Revell
[not found] ` <200407311434.59604.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-31 18:00 ` Lee Revell
2004-08-27 17:45 ` Greg Stark
2004-08-27 17:53 ` Lee Revell
2004-08-27 18:05 ` Bartlomiej Zolnierkiewicz
2004-08-27 18:08 ` Lee Revell
2004-08-27 18:59 ` Bartlomiej Zolnierkiewicz
2004-09-01 13:20 ` Mark Lord
2004-09-01 14:43 ` Jeff Garzik
2004-09-01 15:30 ` Mark Lord
2004-09-01 15:36 ` Mark Lord
2004-09-01 19:36 ` Lee Revell
2004-09-01 18:42 ` Alan Cox
2004-09-01 15:06 ` Alan Cox
2004-09-01 19:08 ` Lee Revell
2004-09-02 16:04 ` Mark Lord
2004-09-01 15:40 ` Bartlomiej Zolnierkiewicz
2004-07-31 18:06 ` Lee Revell
2004-07-31 19:35 ` Alan Cox
2004-07-31 21:35 ` Lee Revell
2004-07-31 21:44 ` Jeff Garzik
2004-07-31 22:12 ` Lee Revell
2004-08-04 17:30 ` Anthony de Boer
2004-08-05 21:39 ` Tim Bird
2004-07-31 0:54 ` Jeff Garzik [this message]
2004-08-03 17:47 ` Mark Lord
2004-08-06 15:48 ` Jeff Garzik
2004-08-06 19:29 ` Tim Bird
2004-08-06 20:46 ` Todd Poynor
2004-08-02 21:56 ` Tim Bird
2004-08-02 21:01 ` Alan Cox
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=410AEDC8.6030901@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
--cc=tpoynor@mvista.com \
/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