From: scott.lawson@intel.com
To: tj@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Scott Lawson <scott.lawson@intel.com>
Subject: [RFC] AHCI: Remove conflicting Intel Lewisburg 3rd-party SATA RAID device IDs
Date: Fri, 26 Feb 2016 10:09:29 -0800 [thread overview]
Message-ID: <1456510169-27138-1-git-send-email-scott.lawson@intel.com> (raw)
From: Scott Lawson <scott.lawson@intel.com>
These PCI device IDs in the AHCI driver conflict with proprietary drivers,
preventing them from loading.
Signed-off-by: Scott Lawson <scott.lawson@intel.com>
---
drivers/ata/ahci.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 546a369..3394492 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -370,11 +370,9 @@ static const struct pci_device_id ahci_pci_tbl[] = {
{ PCI_VDEVICE(INTEL, 0x2826), board_ahci }, /* Lewisburg RAID*/
{ PCI_VDEVICE(INTEL, 0xa182), board_ahci }, /* Lewisburg AHCI*/
{ PCI_VDEVICE(INTEL, 0xa184), board_ahci }, /* Lewisburg RAID*/
- { PCI_VDEVICE(INTEL, 0xa186), board_ahci }, /* Lewisburg RAID*/
{ PCI_VDEVICE(INTEL, 0xa18e), board_ahci }, /* Lewisburg RAID*/
{ PCI_VDEVICE(INTEL, 0xa202), board_ahci }, /* Lewisburg AHCI*/
{ PCI_VDEVICE(INTEL, 0xa204), board_ahci }, /* Lewisburg RAID*/
- { PCI_VDEVICE(INTEL, 0xa206), board_ahci }, /* Lewisburg RAID*/
{ PCI_VDEVICE(INTEL, 0xa20e), board_ahci }, /* Lewisburg RAID*/
/* JMicron 360/1/3/5/6, match class to avoid IDE function */
--
1.9.1
next reply other threads:[~2016-02-27 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 18:09 scott.lawson [this message]
2016-02-27 8:51 ` [RFC] AHCI: Remove conflicting Intel Lewisburg 3rd-party SATA RAID device IDs Christoph Hellwig
2016-02-27 11:20 ` Tejun Heo
[not found] <20160227112033.GX3965 () htj ! duckdns ! org>
2016-02-29 9:28 ` Ocean HY1 He
2016-02-29 9:55 ` Christoph Hellwig
2016-02-29 16:31 ` One Thousand Gnomes
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=1456510169-27138-1-git-send-email-scott.lawson@intel.com \
--to=scott.lawson@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).