From: "Dan Podeanu" <kernel@ccnetwork.com>
To: <linux-kernel@vger.kernel.org>
Subject: megaraid and 2.6.1
Date: Mon, 2 Feb 2004 14:12:48 +0200 [thread overview]
Message-ID: <01db01c3e985$df52e5e0$33e613c2@nod.ro> (raw)
Hello,
Chris Meador's patch regarding megaraid PCI IDs fixup in 2.6.1-rcX didn't
make it
in 2.6.1 so certain megaraid devices (320-1, 320-2, presumably others
aswell) aren't
recognized by 2.6.1.
>From drivers/scsi/megaraid.c:
{PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_AMI_MEGARAID,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
While, according to Chris' patch:
--- linux-2.6.1-rc3.orig/drivers/scsi/megaraid.c 2004-01-08
12:14:51.000000000 -0500
+++ linux-2.6.1-rc3/drivers/scsi/megaraid.c 2004-01-08
12:01:24.000000000 -0500
@@ -5093,7 +5093,7 @@
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
{PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_AMI_MEGARAID3,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
- {PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_AMI_MEGARAID,
+ {PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_AMI_MEGARAID3,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
{0,}
};
Anyone knows whats the status of this problem ? Does the patch fixes it ?
Regards,
Dan.
next reply other threads:[~2004-02-02 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 12:12 Dan Podeanu [this message]
2004-02-02 15:15 ` megaraid and 2.6.1 Chris Meadors
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='01db01c3e985$df52e5e0$33e613c2@nod.ro' \
--to=kernel@ccnetwork.com \
--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