From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: davidsen@tmr.com, linux-kernel@vger.kernel.org, nick.orlov@mail.ru
Subject: Re: [PATCH] pdc20265 problem.
Date: Wed, 7 Aug 2002 12:20:43 +0200 [thread overview]
Message-ID: <1528932608D@vcnet.vc.cvut.cz> (raw)
On 7 Aug 02 at 0:54, Adam J. Richter wrote:
> Nick Orlov writes:
> >But wouldn't it be a cleaner solution if we will have _compile_ time
> >option that by default is turned on in order to handle rare cases,
> >and _can_ be turned off in order to handle _most_ cases without any
> >boot-time options?
>
> Linux users in the "I'm not a sysadmin" crowd (?) probably
> don't care about the scan order of the pdc20265 IDE controller,
> but people in the "I'm a sysadmin, not a programmer" crowd
> may have legitimiate reasons to.
But such "I'm not a sysadmin" people will be very surprised that their
promise was IDE2 in 2.2.x, it was IDE2 in 2.4.18, it is IDE2 in 2.5.30,
and now - oops - it is IDE0 in 2.4.19. Broken, I'd say.
There is an CONFIG_BLK_DEV_OFFBOARD option (apparently unused...),
so use this one, if some distribution must force ide0= to promise
if their installer cannot find master disk on /dev/hde. But changing
behavior for no reason - especially in the middle of stable series -
is IMHO unacceptable.
Fortunately I use 2.5.30's IDE for real work ;-)
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-08-07 10:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 10:20 Petr Vandrovec [this message]
2002-08-07 23:04 ` [PATCH] pdc20265 problem Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Petr Vandrovec
2002-08-08 18:35 ` Andre Hedrick
2002-08-09 6:47 ` Marcin Dalecki
2002-08-12 1:24 ` Andre Hedrick
2002-08-08 16:48 Petr Vandrovec
2002-08-08 17:30 ` Andre Hedrick
2002-08-08 12:45 Petr Vandrovec
2002-08-08 13:02 ` Andre Hedrick
2002-08-07 18:39 Adam J. Richter
2002-08-07 19:33 ` Thunder from the hill
2002-08-07 21:11 ` Alan Cox
2002-08-07 20:02 ` Thunder from the hill
2002-08-07 23:40 ` Alan Cox
2002-08-07 7:54 Adam J. Richter
2002-08-07 11:41 ` Alan Cox
2002-08-07 23:08 ` Bill Davidsen
2002-08-08 10:49 ` Zwane Mwaikambo
2002-08-07 16:32 ` Thunder from the hill
2002-08-06 10:28 Petr Vandrovec
2002-08-02 19:05 Bartlomiej Zolnierkiewicz
2002-08-02 23:05 ` Marcelo Tosatti
2002-08-03 0:55 ` Bartlomiej Zolnierkiewicz
2002-08-03 0:08 ` Marcelo Tosatti
2002-08-03 1:22 ` Nick Orlov
2002-08-03 13:41 ` Alan Cox
2002-08-06 3:48 ` Bill Davidsen
2002-08-06 4:33 ` Nick Orlov
2002-08-07 3:09 ` Bill Davidsen
2002-08-07 3:56 ` Nick Orlov
2002-08-07 18:30 ` Andre Hedrick
2002-08-07 20:27 ` Tomas Szepe
2002-08-07 22:46 ` Bill Davidsen
2002-08-08 10:50 ` Andre Hedrick
2002-08-08 17:42 ` Nick Orlov
2002-08-08 18:02 ` Andre Hedrick
2002-08-09 6:44 ` Marcin Dalecki
2002-08-12 1:37 ` Andre Hedrick
2002-08-09 17:16 ` Bill Davidsen
2002-08-01 6:38 Linux v2.4.19-rc5 Marcelo Tosatti
2002-08-02 1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02 2:29 ` Nick Orlov
2002-08-02 12:27 ` Alan Cox
2002-08-02 12:52 ` Nick Orlov
2002-08-02 14:00 ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45 ` Nick Orlov
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=1528932608D@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=adam@yggdrasil.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.orlov@mail.ru \
/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