From: Jerry Hoemann <jerry.hoemann@hpe.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matt Hsiao <matt.hsiao@hpe.com>,
linux-kernel@vger.kernel.org, arnd@arndb.de,
david.altobelli@hpe.com, mark.rusk@hpe.com
Subject: Re: [PATCH 3/4] misc: hpilo: Do not claim unsupported hardware
Date: Thu, 21 Feb 2019 20:59:24 -0700 [thread overview]
Message-ID: <20190222035924.GA31132@anatevka> (raw)
In-Reply-To: <20190221083515.GC6397@kroah.com>
On Thu, Feb 21, 2019 at 09:35:15AM +0100, Greg KH wrote:
> On Thu, Feb 21, 2019 at 04:04:41PM +0800, Matt Hsiao wrote:
> > Do not claim when SSID 0x0289 as the iLO features
> > are not enabled/validated by the firmware.
>
> Can you put more information here, like _what_ hardware is not being
> supported anymore? As it is, this has nothing to do with "validation by
> the firmware", you are just deciding to not support a device that
> previously was supported by this driver. As such you should provide
> more information why you are taking away functionality.
Hi Greg,
The SSID 0x0289 correspond to the recent CL2600/CL2800 servers. These servers
leveraged Proliant hardware but are targeted to a different market segment
with different requirements. They also come with a different firmware base.
Based upon the targeted market needs, these server de-featured certain
aspects of Proliants with this being one.
As a result, the linux hpilo driver still claims the hardware but
is not functional.
We decided to blacklist the driver to reduce confusion to customers.
Matt will update the documentation in the second version of the patch set.
Hope this helps.
Take care,
Jerry
--
-----------------------------------------------------------------------------
Jerry Hoemann Software Engineer Hewlett Packard Enterprise
-----------------------------------------------------------------------------
next prev parent reply other threads:[~2019-02-22 3:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 8:04 [PATCH 0/4] misc: hpilo: Do not claim on unsupported hardware Matt Hsiao
2019-02-21 8:04 ` [PATCH 1/4] misc: hpilo: Be more specific when ignoring the aux iLO Matt Hsiao
2019-02-21 8:04 ` [PATCH 2/4] misc: hpilo: Exclude unsupported device via blacklist Matt Hsiao
2019-02-21 8:33 ` Greg KH
2019-02-22 4:35 ` Jerry Hoemann
2019-02-22 6:50 ` Greg KH
2019-02-21 8:04 ` [PATCH 3/4] misc: hpilo: Do not claim unsupported hardware Matt Hsiao
2019-02-21 8:35 ` Greg KH
2019-02-22 3:59 ` Jerry Hoemann [this message]
2019-02-21 8:04 ` [PATCH 4/4] misc: hpilo: Update driver version Matt Hsiao
2019-02-21 8:32 ` Greg KH
2019-02-22 4:11 ` Jerry Hoemann
2019-02-22 6:49 ` Greg KH
2019-02-25 8:28 ` Jerry Hoemann
2019-02-25 21:44 ` Greg KH
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=20190222035924.GA31132@anatevka \
--to=jerry.hoemann@hpe.com \
--cc=arnd@arndb.de \
--cc=david.altobelli@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rusk@hpe.com \
--cc=matt.hsiao@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