From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Orlov <nick.orlov@mail.ru>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pdc20265 problem.
Date: 03 Aug 2002 14:41:23 +0100 [thread overview]
Message-ID: <1028382083.31733.34.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020803012204.GA9047@nikolas.hn.org>
On Sat, 2002-08-03 at 02:22, Nick Orlov wrote:
> I think that question is _how often_ pdc20265 is used as primary
> controller? Actually I know a lot of mobos with pdc20265 as additional
> controller (and I don't see the one that uses it as primary).
>
> Don't forget about "ide=reverse" parameter that allows you to treat
> pdc20265 as primary if by default kernel treat pdc20265 as secondary.
>
> So I don't see _any_ reason to force pdc20265 to be primary (onboard)
> unless CONFIG_PDC202XX_FORCE is set.
This is the wrong question.
The right question for a stable kernel is "Why isnt it behaving
precisely the same way as it did before the merge". What got confused in
the _FORCE stuff. Why did _FORCE checks even get into the raid probe not
another config option...
next prev parent reply other threads:[~2002-08-03 12:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
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 15:37 ` [PATCH] " Nick Orlov
2002-08-03 18:29 ` Nick Orlov
2002-08-03 1:22 ` Nick Orlov
2002-08-03 13:41 ` Alan Cox [this message]
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
-- 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 10:20 Petr Vandrovec
2002-08-07 23:04 ` Bill Davidsen
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-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=1028382083.31733.34.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®