From: Matt Hsiao <matt.hsiao@hpe.com>
To: linux-kernel@vger.kernel.org
Cc: arnd@arndb.de, gregkh@linuxfoundation.org,
david.altobelli@hpe.com, mark.rusk@hpe.com,
jerry.hoemann@hpe.com, Matt Hsiao <matt.hsiao@hpe.com>
Subject: [PATCH v2 2/2] misc: hpilo: Do not claim unsupported hardware
Date: Wed, 27 Feb 2019 11:25:30 +0800 [thread overview]
Message-ID: <1551237930-28823-3-git-send-email-matt.hsiao@hpe.com> (raw)
In-Reply-To: <1551237930-28823-1-git-send-email-matt.hsiao@hpe.com>
CL2600/CL2800 servers leveraged Proliant hardware but are targeted to a
different market segment and come with a different firmware base. Based
upon targeted market needs, the servers de-featured certain aspects of iLO.
As a result, hpilo driver still claims the hardware but is not functional,
so we decided to blacklist it with SSID 0x0289 to reduce confusion to
customers.
Signed-off-by: Matt Hsiao <matt.hsiao@hpe.com>
---
drivers/misc/hpilo.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/hpilo.c b/drivers/misc/hpilo.c
index 0224e50..927309b 100644
--- a/drivers/misc/hpilo.c
+++ b/drivers/misc/hpilo.c
@@ -32,6 +32,8 @@
static const struct pci_device_id ilo_blacklist[] = {
/* auxiliary iLO */
{PCI_DEVICE_SUB(PCI_VENDOR_ID_HP, 0x3307, PCI_VENDOR_ID_HP, 0x1979)},
+ /* CL */
+ {PCI_DEVICE_SUB(PCI_VENDOR_ID_HP, 0x3307, PCI_VENDOR_ID_HP_3PAR, 0x0289)},
{}
};
--
1.8.3.1
prev parent reply other threads:[~2019-02-27 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 3:25 [PATCH v2 0/2] misc: hpilo: Do not claim on unsupported hardware Matt Hsiao
2019-02-27 3:25 ` [PATCH v2 1/2] misc: hpilo: Exclude unsupported device via blacklist Matt Hsiao
2019-02-27 3:25 ` Matt Hsiao [this message]
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=1551237930-28823-3-git-send-email-matt.hsiao@hpe.com \
--to=matt.hsiao@hpe.com \
--cc=arnd@arndb.de \
--cc=david.altobelli@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=jerry.hoemann@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rusk@hpe.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;
as well as URLs for NNTP newsgroup(s).