From: Matt Domsch <Matt_Domsch@dell.com>
To: "Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: 'Chris Adams' <cmadams@hiwaay.net>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: Why are MegaRAID drivers mutually exclusive?
Date: Wed, 10 Nov 2004 13:42:21 -0600 [thread overview]
Message-ID: <20041110194221.GA28524@lists.us.dell.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570562C128@exa-atlanta>
On Wed, Nov 10, 2004 at 02:24:06PM -0500, Bagalkote, Sreenivas wrote:
> The new and old drivers are mutually exclusive to the extent that
> both cannot be loaded simultaneously as they both work on same
> hardware. It only seems logical that this exclusivity is represented
> in Kconfig as well.
There are three issues here that need to be addressed.
1) megaraid_mbox doesn't currently handle all of Chris's hardware.
It's missing some PCI IDs which it should be able to handle.
101e:1960 101e:0475, aka PCI_VENDOR_ID_AMI, PCI_DEVICE_ID_AMI_MEGARAID3
PCI_DEVICE_ID_AMI, PCI_SUBSYS_ID_PERC3_SC
2) megaraid_mbox doesn't handle other sets of hardware it should be
able to handle (Dell PERC2/{SC,DC}). I am not sure why.
3) no megaraid_ioport driver has ever been produced, which was the
original reason for splitting megaraid_mm and megaraid_mbox. This
driver is necessary for Chris's other older hardware.
PCI 101e:9010, aka PCI_VENDOR_ID_AMI, PCI_DEVICE_ID_MEGARAID
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-11-10 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 19:24 Why are MegaRAID drivers mutually exclusive? Bagalkote, Sreenivas
2004-11-10 19:38 ` Chris Adams
2004-11-10 19:42 ` Matt Domsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-10 22:21 Mukker, Atul
2004-11-10 21:25 Mukker, Atul
2004-11-10 22:08 ` Matt Domsch
2004-11-11 8:01 ` Arjan van de Ven
2004-11-11 14:07 ` Chris Adams
2004-11-11 14:24 ` Arjan van de Ven
2004-11-11 14:31 ` Chris Adams
2004-11-11 14:39 ` Arjan van de Ven
2004-11-11 14:42 ` Chris Adams
2004-11-10 18:31 Xose Vazquez Perez
2004-11-10 17:04 Chris Adams
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=20041110194221.GA28524@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=cmadams@hiwaay.net \
--cc=linux-scsi@vger.kernel.org \
--cc=sreenib@lsil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.