mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Jakub Bogusz <qboosh@pld-linux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (2.6 IDE) why PDC202XX_FORCE not allowed with BLK_DEV_PDC202XX_NEW=m?
Date: Sun, 7 Mar 2004 22:36:12 +0100	[thread overview]
Message-ID: <200403072236.12019.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040307210701.GA23440@satan.blackhosts>


[ Please use linux-ide@vger.kernel.org for IDE issues. ]

On Sunday 07 of March 2004 22:07, Jakub Bogusz wrote:
> PDC202XX_FORCE option is needed to override controller disable by BIOS
> when RAID is used. Or maybe there is another way to do this in 2.6.x?

Nope.

> This option has "depends on BLK_DEV_PDC202XX_NEW=y" flag in
> drivers/ide/Kconfig, thus is not available with pdc202xx_new in
> module - why?

It seems like a leftover from non-modular IDE PCI days.

> I saw success report with modular pdc202xx_new after this simple change
> (without PDC202XX_FORCE controller ports were not detected):
>
> --- linux/drivers/ide/Kconfig.orig        2004-03-04 07:16:45.000000000
> +0100 +++ linux/drivers/ide/Kconfig     2004-03-07 17:37:25.000000000 +0100
> @@ -720,7 +720,7 @@
>  # FIXME - probably wants to be one for old and for new
>  config PDC202XX_FORCE
>         bool "Enable controller even if disabled by BIOS"
> -       depends on BLK_DEV_PDC202XX_NEW=y
> +       depends on BLK_DEV_PDC202XX_NEW
>         help
>           Enable the PDC202xx controller even if it has been disabled in
> the BIOS setup.
>
>
> The same may apply to PDC202XX_BURST for pdc202xx_old module...
> (but not tested)

Yes, you are right.

Thanks,
Bartlomiej


      reply	other threads:[~2004-03-07 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 21:07 Jakub Bogusz
2004-03-07 21:36 ` Bartlomiej Zolnierkiewicz [this message]

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=200403072236.12019.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qboosh@pld-linux.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

all inboxes | Powered by JetHome®