All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: SATA hotplug notifications for BMC inventory updates
Date: Thu, 15 Sep 2022 18:32:31 +0300	[thread overview]
Message-ID: <YyNFj1bQLAUtnwFz@home.paul.comp> (raw)
In-Reply-To: <a1414f37-6d90-4a56-ac9b-089dac21f00f@linux.intel.com>

Hello Jason,

Thank you very much for the reply, please see inline.

On Fri, Sep 09, 2022 at 03:19:45PM -0600, Bills, Jason M wrote:
> > The transition to RAID controller has initiated an investigation into
> > what Intel may be willing to enable regarding OBMC.
> 
> I have reached out to some of our RAID team internally.  They have a
> software-based management solution that they use, today, but it only covers
> NVMe-MI based drives.
> 
> I also asked about documentation that may help with this, but since they
> only support NVMe-MI, they don't have much info about SATA support.

I have seen the Intel VROC slides [0], and they mention some
facilities for integration with BMCs. I assumed they're generic for
all the hardware handled by VROC (including SATA as RSTe was
apparently made part of VROC) but now that I re-read it, I see "NVMe
RAID BMC OOB management via OS, UEFI OOB management coming with Intel
VROC 8.0" is apparently NVMe-specific.

So even if this is not useful for Tioga Pass it would still be nice to
support this feature from OpenBMC side for the next generation
servers, and we plan to work on that.

> I'd als recommend contacting your Intel support representative to ask about
> relevant documentation.

Due to the horrible actions of Russia we are no longer permitted to
talk to the Intel support representatives. So we have to count on open
documentation and communication, and we are willing to share
everything useful with the OpenBMC upstream.


[0] https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/vroc-overview.pdf
-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  reply	other threads:[~2022-09-15 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 11:11 SATA hotplug notifications for BMC inventory updates Paul Fertser
2022-09-06 15:53 ` Johnathan Mantey
     [not found]   ` <17841662532977@mail.yandex-team.ru>
2022-09-07 14:04     ` Johnathan Mantey
2022-09-07 14:26       ` Paul Fertser
2022-09-07 14:16   ` Paul Fertser
2022-09-07 14:36     ` Johnathan Mantey
2022-09-09  8:32       ` Paul Fertser
2022-09-09 14:12         ` Johnathan Mantey
2022-09-09 21:19           ` Bills, Jason M
2022-09-15 15:32             ` Paul Fertser [this message]
2022-09-15 15:05           ` Paul Fertser

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=YyNFj1bQLAUtnwFz@home.paul.comp \
    --to=fercerpav@gmail.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.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 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.