From: Adriana Kobylak <anoo@linux.ibm.com>
To: Gunnar Mills <gmills@linux.vnet.ibm.com>
Cc: "Alexander A. Filippov" <a.filippov@yadro.com>,
openbmc@lists.ozlabs.org, jandraara@gmail.com,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: Packaging and deploying multiple firmware image types in one
Date: Tue, 12 Nov 2019 18:54:13 -0600 [thread overview]
Message-ID: <6cd66e8841aedf1b7a0508cd19ef8e4e@linux.vnet.ibm.com> (raw)
In-Reply-To: <cf5656dc-0beb-e198-24cc-2109b9ca42d9@linux.vnet.ibm.com>
On 2019-11-12 15:38, Gunnar Mills wrote:
> On 11/12/2019 1:49 AM, Alexander A. Filippov wrote:
>> On Mon, Nov 11, 2019 at 01:28:11PM -0600, Adriana Kobylak wrote:
>>
>> 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.
>
> IBM is planning on supporting a bundled "System" firmware form the
> WebUI.
> The design is here:
> https://ibm.invisionapp.com/share/4XNZ0JAMJ7B#/screens/319215228
>
Maybe in the mean time we can have the WebUI display the "System"
versions alongside the "BMC" ones. I'll check if it's as simple as "if
purpose is BMC or System" do what it currently does.
>>> [3]
>>> https://github.com/openbmc/meta-openpower/blob/master/recipes-phosphor/flash/host-fw_git.bb
>>>
next prev parent reply other threads:[~2019-11-13 0:52 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
2019-11-12 21:38 ` Gunnar Mills
2019-11-13 0:54 ` Adriana Kobylak [this message]
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=6cd66e8841aedf1b7a0508cd19ef8e4e@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=a.filippov@yadro.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=jandraara@gmail.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--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.