From: Kronos <kronos@kronoz.cjb.net>
To: linux-kernel@vger.kernel.org
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: Linux 2.4.25-pre4
Date: Tue, 6 Jan 2004 18:30:17 +0100 [thread overview]
Message-ID: <20040106173017.GA10755@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040106102819.A12626@lists.us.dell.com>
Matt Domsch <Matt_Domsch@dell.com> ha scritto:
>> Trying to compile $subj with following config (these options seem to
>> cause the problem, full config attached):
>>
>> CONFIG_SCSI_MEGARAID=y
>> CONFIG_SCSI_MEGARAID2=y
>>
>> Is this a known issue and megaraids can't live together, or am I
>> supposed to be able to compile both drivers in and this is a bug?
>
> yes, this is known and expected. You can build both as modules, but
> they're not intended to both be loaded simultaneously (either built-in
> or as modules). They're mutually exclusive.
Ok, what about this patch (against 2.4.25-pre4):
--- linux-2.4/drivers/scsi/Config.in.orig Tue Jan 6 18:11:10 2004
+++ linux-2.4/drivers/scsi/Config.in Tue Jan 6 18:23:29 2004
@@ -66,8 +66,13 @@
dep_tristate 'AdvanSys SCSI support' CONFIG_SCSI_ADVANSYS $CONFIG_SCSI
dep_tristate 'Always IN2000 SCSI support' CONFIG_SCSI_IN2000 $CONFIG_SCSI
dep_tristate 'AM53/79C974 PCI SCSI support' CONFIG_SCSI_AM53C974 $CONFIG_SCSI $CONFIG_PCI
-dep_tristate 'AMI MegaRAID support' CONFIG_SCSI_MEGARAID $CONFIG_SCSI
-dep_tristate 'AMI MegaRAID2 support' CONFIG_SCSI_MEGARAID2 $CONFIG_SCSI
+
+if [ "$CONFIG_SCSI_MEGARAID2" == "n" -o "$CONFIG_SCSI_MEGARAID2" == "" ]; then
+ dep_tristate 'AMI MegaRAID support' CONFIG_SCSI_MEGARAID $CONFIG_SCSI
+fi
+if [ "$CONFIG_SCSI_MEGARAID" == "n" -o "$CONFIG_SCSI_MEGARAID" == "" ]; then
+ dep_tristate 'AMI MegaRAID2 support' CONFIG_SCSI_MEGARAID2 $CONFIG_SCSI
+fi
dep_tristate 'BusLogic SCSI support' CONFIG_SCSI_BUSLOGIC $CONFIG_SCSI
if [ "$CONFIG_SCSI_BUSLOGIC" != "n" ]; then
I'm not very familiar with 2.4 config language, maybe there's a better
way to do it.
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Carpe diem, quam minimum credula postero. (Q. Horatius Flaccus)
next prev parent reply other threads:[~2004-01-06 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 14:14 Marcelo Tosatti
2004-01-06 16:16 ` Jan Kokoska
2004-01-06 16:28 ` Matt Domsch
2004-01-06 17:30 ` Kronos [this message]
2004-01-06 18:26 ` Adrian Bunk
2004-01-06 18:02 ` Mike Fedyk
2004-01-06 18:21 ` Marcelo Tosatti
2004-01-30 13:57 ` Andreas Metzler
2004-01-30 15:19 ` Markus Hästbacka
2004-01-31 22:47 ` Marcelo Tosatti
2004-01-31 23:11 ` Andreas Metzler
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 16:15 Andrzej Krzysztofowicz
2004-01-07 15:34 Andrzej Krzysztofowicz
[not found] <1b0nY-2vi-13@gated-at.bofh.it>
[not found] ` <1b3OA-7FV-17@gated-at.bofh.it>
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=20040106173017.GA10755@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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®