From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andre Hedrick <andre@linux-ide.org>,
"Heater, Daniel (IndSys, GEFanuc,
VMIC)" <Daniel.Heater@gefanuc.com>,
"'Padraig Brady'" <padraig.brady@corvil.com>,
"'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: IDE-flash device and hard disk on same controller
Date: Thu, 22 Aug 2002 21:26:04 -0400 [thread overview]
Message-ID: <3D658F2C.1080400@mandrakesoft.com> (raw)
In-Reply-To: m1ofbupfe1.fsf@frodo.biederman.org
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 DEVICE
> DIAGNOSTICS 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. I would
prefer to barf if the BSY or DRDY bits are set, because taking over the
ATA bus while a device is in the middle of a command shouldn't be
happening at Linux kernel boot, ever.
Jeff
next prev parent reply other threads:[~2002-08-23 1:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 19:52 IDE-flash device and hard disk on same controller 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-21 6:57 ` MMIO {Re: IDE-flash device and hard disk on same controller} Andre Hedrick
2002-08-21 7:10 ` Andre Hedrick
2002-08-22 5:34 ` IDE-flash device and hard disk on same controller 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 [this message]
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
-- 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-23 6:54 Adam J. Richter
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
2002-08-21 13:22 Warner, Bill (IndSys, GEFanuc, VMIC)
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=3D658F2C.1080400@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Daniel.Heater@gefanuc.com \
--cc=andre@linux-ide.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig.brady@corvil.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