From: "Alexander A. Filippov" <a.filippov@yadro.com>
To: <openbmc@lists.ozlabs.org>
Subject: Re: Packaging and deploying multiple firmware image types in one
Date: Tue, 12 Nov 2019 10:49:21 +0300 [thread overview]
Message-ID: <20191112074921.GA4938@bbwork.lan> (raw)
In-Reply-To: <d9a820f4778cc2964d6f0a9b8a78d722@linux.vnet.ibm.com>
On Mon, Nov 11, 2019 at 01:28:11PM -0600, Adriana Kobylak wrote:
> There was some discussion in the "PSU firmware update" proposal[1] about
> bundling firmware images together such as the BMC and PSU firmware. The
> Software interface defines these bundles as a "System" version[2].
>
> At IBM, we're starting to create a "System" bundle of BMC + host firmware by
> adding a recipe that would add the host's firmware files to the BMC's
> squashfs[3].
>
> One of the pending items is determining how to showcase the version of these
> System images in Redfish. We can assume that the version of a System image
> corresponds to the BMC's "FirmwareVersion", but it's unknown what else the
> bundle contains (host fw, PSU fw, PCIe fw,..), in order to populate the
> other version fields such as "BiosVersion". There's a D-Bus "Extended
> Version" property[4] that could be leveraged to add the additional image
> information.
>
> Feel free to share if you have any thoughts on this item or any aspect of
> these "System" images.
>
We use the system bundle of BMC + Host firmware on our VESNIN hardware.
There are some things which cause discomfort a little bit:
- The uploaded system bundle isn't shown in the WebUI.
- The system bundle has only one version field which is common for BMC and Host
firmwares.
- After rebooting BMC, which is required to complete update the BMC firmware
the system bundle turns to two separated instances in D-Bus which has its own
real versions.
Thus, I thought about putting the separate manifests for each part of the
bundle.
>
> ---
> [1] https://lists.ozlabs.org/pipermail/openbmc/2019-June/016573.html
> [2] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Software/Version.interface.yaml
> [3] https://github.com/openbmc/meta-openpower/blob/master/recipes-phosphor/flash/host-fw_git.bb
> [4] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Software/ExtendedVersion.interface.yaml
next prev parent reply other threads:[~2019-11-12 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:28 Packaging and deploying multiple firmware image types in one Adriana Kobylak
2019-11-12 7:49 ` Alexander A. Filippov [this message]
2019-11-12 21:38 ` Gunnar Mills
2019-11-13 0:54 ` Adriana Kobylak
2019-11-12 22:54 ` Adriana Kobylak
2019-11-13 7:24 ` Alexander A. Filippov
2019-11-14 7:51 ` Alexander A. Filippov
2019-11-14 22:10 ` Adriana Kobylak
2019-11-15 14:51 ` Adriana Kobylak
2019-11-15 15:46 ` Andrew Geissler
2019-11-19 19:22 ` Adriana Kobylak
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=20191112074921.GA4938@bbwork.lan \
--to=a.filippov@yadro.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.