mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: jgarzik@mandrakesoft.com
Cc: ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: IDE-flash device and hard disk on same controller
Date: Thu, 22 Aug 2002 23:54:03 -0700	[thread overview]
Message-ID: <200208230654.XAA02328@adam.yggdrasil.com> (raw)

Jeff Garzik wrote:
>Eric W. Biederman wrote:
>>The problem is that immediately after bootup ATA devices do not respond until
>>their media has spun up.  Which is both required by the spec, and observed in
>>practice.   Which is likely a problem if this code is run a few seconds after
>>bootup.  Which makes it quite possible the drive will ignore the
>>EXECUTE DEVICEDIAGNOSTICS and your error code won't be valid when 
>>the bsy flag clears.   I don't know how serious that would be. 
>
>
>Well, this only applies if you are slack and letting the kernel init 
>your ATA from scratch, instead of doing proper ATA initialization in 
>firmware ;-)
>
>Seriously, if you are a handed an ATA device that is actually in 
>operation when the kernel boots, you are already out of spec.

	1. Regardless of whatever specification you are referring to
or Andre's "31 second rule of [Power On Self Test]", it is genuinely
useful to boot faster by overlapping some other kernel work before the
drive is.  Specifications ultimately exist only to serve this
usefulness.  When a specification impedes usefulness, sometimes it's
the right decision to violate it.  Of course, we're not talking about
your IDE code violating such a specification, but rather not relying
on this particular guarantee.

	2. Besides, if this code is supposed to be a generic IDE core,
it many need to run on platforms that do not provide that guarantee or
where the boot code is not even capable of finding where all of the
IDE controllers.

	3. In the hierarchy of upgradability, it is generally easier
to replace the kernel than the Power On Self Test, which is more often
in flash or ROM, and which may require help from an unenthusiastic
hardware vendor.  So, it is better to weight trade-offs a few notches
in favor of avoid reliance on guarantees about the Power On Self Test.

	If I understand correctly, the cost of this trade off would be
adding one or two lines that add perhaps 20 bytes and as many CPU
cycles at initiailzation (except when this change really is necessary).

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-08-23  6:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  6:54 Adam J. Richter [this message]
2002-08-23  7:45 ` Andre Hedrick
2002-08-23 11:10   ` Russell King
2002-08-23 17:08     ` Andre Hedrick
2002-08-23 17:42       ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-08-23 10:48 Adam J. Richter
2002-08-23 10:14 Adam J. Richter
2002-08-23  8:31 Adam J. Richter
2002-08-23  8:59 ` Andre Hedrick
2002-08-23  9:54 ` Andries Brouwer
2002-08-21 13:22 Warner, Bill (IndSys, GEFanuc, VMIC)
2002-08-20 19:52 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-08-20 21:57 ` Andre Hedrick
2002-08-20 22:00   ` Jeff Garzik
2002-08-20 22:28     ` Jeff Garzik
2002-08-21  6:36       ` Geert Uytterhoeven
2002-08-21  6:55         ` Andre Hedrick
2002-08-21  7:16           ` Geert Uytterhoeven
2002-08-22  5:34       ` Eric W. Biederman
2002-08-22 23:12         ` Jeff Garzik
2002-08-23  0:50           ` Eric W. Biederman
2002-08-23  1:26             ` Jeff Garzik
2002-08-23 11:03               ` Russell King
2002-08-23 11:41               ` Benjamin Herrenschmidt
2002-08-23 10:12                 ` Alan Cox
2002-08-23 13:09               ` Eric W. Biederman
2002-08-23  3:14             ` Andre Hedrick
2002-08-23 11:44               ` Benjamin Herrenschmidt
2002-08-24  2:02                 ` Jeff Garzik
2002-08-24  0:19                   ` Benjamin Herrenschmidt
2002-08-24  8:41                   ` Russell King
2002-08-24 20:28                     ` Andre Hedrick
2002-08-23  3:19             ` Andre Hedrick
2002-08-23  7:14               ` Helge Hafting
2002-08-23  7:49                 ` Andre Hedrick
2002-08-23 10:50               ` Geert Uytterhoeven
2002-08-23 11:08                 ` Russell King
2002-08-23 11:07               ` Russell King
2002-08-23 11:36           ` Benjamin Herrenschmidt
2002-08-22 13:41 ` bill davidsen
2002-08-19 18:31 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-08-19 19:21 ` Alan Cox
2002-08-20  8:44 ` Padraig Brady

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=200208230654.XAA02328@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=ebiederm@xmission.com \
    --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

all inboxes | Powered by JetHome®