From: Nick Orlov <nick.orlov@mail.ru>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pdc20265 problem.
Date: Fri, 2 Aug 2002 21:22:04 -0400 [thread overview]
Message-ID: <20020803012204.GA9047@nikolas.hn.org> (raw)
In-Reply-To: <Pine.SOL.4.30.0208030241540.18115-100000@mion.elka.pw.edu.pl>
On Sat, Aug 03, 2002 at 02:55:21AM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> On Fri, 2 Aug 2002, Marcelo Tosatti wrote:
> > On Fri, 2 Aug 2002, Bartlomiej Zolnierkiewicz wrote:
> > > > Just FYI,
> > > >
> > > > before these "#ifdef" fixes it was treated as OFF_BOARD unless
> > > > CONFIG_PDC202XX_FORCE is set. (now it's inverted)
> > >
> > > This should be fixed.
> >
> > If we change the #ifdef on ide-pci.c it will skip some controllers which
> > worked before _without_ CONFIG_PDC202XX_FORCE set.
>
> I was thinking about changing it globally to do what its name suggest.
>
> Main problem is that before introducing skipping Promises, FORCE
> controlled overriding BIOS only (?) and now it is also used to control
> 'skipping'. (FORCE should be by default on of course)
> Probably 'skipping' should be separated to another config option...
>
> And second problem is that 20265 is used as primary onboard
> sometimes and sometimes as offboard (another config option?).
>
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.
--
With best wishes,
Nick Orlov.
next prev parent reply other threads:[~2002-08-03 1:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 19:05 [PATCH] pdc20265 problem 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 [this message]
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
-- 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=20020803012204.GA9047@nikolas.hn.org \
--to=nick.orlov@mail.ru \
--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