From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: IDE-flash device and hard disk on same controller
Date: 22 Aug 2002 13:41:24 GMT [thread overview]
Message-ID: <ak2pm4$6dv$1@gatekeeper.tmr.com> (raw)
In-Reply-To: A9713061F01AD411B0F700D0B746CA6802FC1464@vacho6misge.cho.ge.com
In article <A9713061F01AD411B0F700D0B746CA6802FC1464@vacho6misge.cho.ge.com>,
Heater, Daniel (IndSys, GEFanuc, VMIC) <Daniel.Heater@gefanuc.com> wrote:
| OK. hdc=flash works where hdc=hard drive and hdd=CompactFlash.
|
| Thanks Padraig.
|
| I guess it's 6 of one, half-dozen the other, but telling the kernel that my
| hard drive is a flash drive just makes me feel squidgy! I'm still inclined
| to suggest that the test that _prevents_ hard drive + CF configuration is no
| longer appropriate now that _some_ (most??) hardware vendors have figured
| out how to get ide-flash devices to work without "hanging" when no second
| device is present. Users with incompatible hardware can still prevent the
| long system hang by using hdx=none.
I think that traditionally people with broken hardware have been the
ones to use parameters to warn the kernel about them. I certainly have
run some ill-behaved hardware that way ;-) Since there is now and will
be in the future more correct systems than broken, it would seem that
the default would be to work with correct systems.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-08-22 13:43 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
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 [this message]
-- 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='ak2pm4$6dv$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.