* (2.6 IDE) why PDC202XX_FORCE not allowed with BLK_DEV_PDC202XX_NEW=m?
@ 2004-03-07 21:07 Jakub Bogusz
2004-03-07 21:36 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 2+ messages in thread
From: Jakub Bogusz @ 2004-03-07 21:07 UTC (permalink / raw)
To: linux-kernel
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?
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?
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)
--
Jakub Bogusz http://cyber.cs.net.pl/~qboosh/
PLD Team http://www.pld-linux.org/
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: (2.6 IDE) why PDC202XX_FORCE not allowed with BLK_DEV_PDC202XX_NEW=m?
2004-03-07 21:07 (2.6 IDE) why PDC202XX_FORCE not allowed with BLK_DEV_PDC202XX_NEW=m? Jakub Bogusz
@ 2004-03-07 21:36 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 2+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-03-07 21:36 UTC (permalink / raw)
To: Jakub Bogusz; +Cc: linux-kernel
[ 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-03-07 21:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-07 21:07 (2.6 IDE) why PDC202XX_FORCE not allowed with BLK_DEV_PDC202XX_NEW=m? Jakub Bogusz
2004-03-07 21:36 ` Bartlomiej Zolnierkiewicz
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®