From: Matt Spinler <mspinler@linux.vnet.ibm.com>
To: Sai Dasari <sdasari@fb.com>
Cc: Vernon Mauery <vernon.mauery@linux.intel.com>,
Patrick Venture <venture@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
openbmc
<openbmc-bounces+mspinler=linux.vnet.ibm.com@lists.ozlabs.org>
Subject: Re: In-Band Firmware Update
Date: Tue, 24 Jul 2018 15:38:05 -0500 [thread overview]
Message-ID: <6491f54b7b2da630cd3796c6bc3a5214@linux.vnet.ibm.com> (raw)
In-Reply-To: <7BB65E38-8F1D-4723-B1C5-74102D4D0B20@fb.com>
On 2018-07-23 19:13, Sai Dasari wrote:
> Any thoughts on reusing/leveraging the PICMG's hpm spec @
> https://www.picmg.org/openstandards/hardware-platform-management/ .
> One of the benefit would be the standard 'ipmitool' has native support
> for the update and changes are limited to BMC f/w.
> On a downside, the firmware binary has to be repackaged as .hpm format
> for this protocol to do some preparation steps as it support multiple
> f/w components in a single package.
This was brought up a few months ago and decided against:
https://lists.ozlabs.org/pipermail/openbmc/2017-November/009938.html
We are going to investigate using the DFU protocol, as that
also has host side tools already available.
>
> --Vernon
next prev parent reply other threads:[~2018-07-24 20:31 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
2018-07-24 0:13 ` Sai Dasari
2018-07-24 19:02 ` Bakshi, Sachit
2018-07-24 20:38 ` Matt Spinler [this message]
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=6491f54b7b2da630cd3796c6bc3a5214@linux.vnet.ibm.com \
--to=mspinler@linux.vnet.ibm.com \
--cc=openbmc-bounces+mspinler=linux.vnet.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sdasari@fb.com \
--cc=venture@google.com \
--cc=vernon.mauery@linux.intel.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.