From: Patrick Williams <patrick@stwcx.xyz>
To: Jayashree D <jayashree-d@hcl.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>
Subject: Re: Read Firmware Versions
Date: Wed, 23 Sep 2020 10:35:10 -0500 [thread overview]
Message-ID: <20200923153510.GP6152@heinlein> (raw)
In-Reply-To: <SG2PR04MB3093A25A217B7E1FFD65D8A8E13B0@SG2PR04MB3093.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Tue, Sep 22, 2020 at 01:34:50PM +0000, Jayashree D wrote:
> Classification: HCL Internal
>
> Thanks Patrick for your response.
>
> In phosphor-bmc-code-mgmt, I am seeing the software image is upgraded and based on the image update, version is updated.
> But in my platform, I have to read firmware versions using oem commands and that version should be displayed under dbus objects.
> Whether phosphor-bmc-code-mgmt repo will be suitable to display the firmware version using dbus objects?
Vijay recently added a simple BIOS flash management to
phosphor-bmc-code-mgmt, but there is also a openpower-pnor-code-mgmt for
the equivalent of BIOS management on openpower systems. Since your code
update scheme is likely to be specific to your IPMB commands, I don't
know if that would be best in a separate repository or an extension onto
phosphor-bmc-code-mgmt.
Adriana, any opinions?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-23 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 14:12 Read Firmware Versions Jayashree D
2020-09-21 15:23 ` Patrick Williams
2020-09-21 15:23 ` Patrick Williams
2020-09-22 13:34 ` Jayashree D
2020-09-22 20:52 ` Vijay Khemka
2020-09-23 15:35 ` Patrick Williams [this message]
2020-09-23 20:17 ` Adriana Kobylak
2020-09-24 1:39 ` Vijay Khemka
2020-09-24 2:36 ` Lei Yu
2020-09-25 11:49 ` Jayashree D
2020-10-01 15:19 ` Jayashree D
2020-10-02 20:58 ` Vijay Khemka
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=20200923153510.GP6152@heinlein \
--to=patrick@stwcx.xyz \
--cc=jayashree-d@hcl.com \
--cc=openbmc@lists.ozlabs.org \
--cc=velumanit@hcl.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.