From: Vernon Mauery <vernon.mauery@linux.intel.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: In-Band Firmware Update
Date: Mon, 23 Jul 2018 15:18:37 -0700 [thread overview]
Message-ID: <20180723221837.GI105329@mauery> (raw)
In-Reply-To: <CAO=notyCMVrJ9Ya+PaukB1k1M7KE07ZHnD5prt4CsA0gdfe+qw@mail.gmail.com>
On 23-Jul-2018 11:13 AM, Patrick Venture wrote:
>I've started to implement the host-tool outside of google3, and
>started splitting up the OEM handler that corresponds with it.
>However, firstly, I've submitted the design for the protocol for
>review, please let me know if you're interested and I'll add you to
>the review. IIRC, there was at least one interested party outside of
>us.
I am interested in coming up with a common (OpenBMC OEM level) set of
Firmware NetFn commands that will allow all users of OpenBMC to be able
to use common, open-source utilities to do firmware updates. If they are
IPMI commands, this would include in-band (with KCS/BT for
command/control and USB for transfer) or out-of-band (over RMCP+).
Rather than use the OEM NetFn, for firmware updates, we should be using
the Firmware NetFn. The entire Firmware NetFn is considered to be OEM
per the IPMI spec. I would propose that we simply provide a common
implementation for OpenBMC (as a provider library, of course, so it
could be replaced if a downstream OEM doesn't want it).
--Vernon
next prev parent reply other threads:[~2018-07-23 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 18:13 In-Band Firmware Update Patrick Venture
2018-07-23 22:18 ` Vernon Mauery [this message]
2018-07-24 0:13 ` Sai Dasari
2018-07-24 19:02 ` Bakshi, Sachit
2018-07-24 20:38 ` Matt Spinler
2018-07-27 19:01 ` Patrick Venture
2018-08-06 16:51 ` Patrick Venture
2018-08-06 17:26 ` Patrick Venture
2018-08-06 18:36 ` Patrick Venture
2018-08-06 22:20 ` Ed Tanous
2018-08-06 23:04 ` Andrew Jeffery
2018-08-07 15:14 ` Patrick Venture
2018-08-07 16:41 ` Patrick Venture
2018-08-07 18:48 ` Patrick Venture
2018-08-07 15:11 ` Patrick Venture
2018-08-06 21:59 ` Ed Tanous
2018-08-08 1:32 ` Jeremy Kerr
2018-08-08 21:42 ` Vernon Mauery
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=20180723221837.GI105329@mauery \
--to=vernon.mauery@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.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 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.