From: Vijay Khemka <vijaykhemka@fb.com>
To: Jayashree D <jayashree-d@hcl.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Lei Yu <yulei.sh@bytedance.com>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: Read Firmware Versions
Date: Fri, 2 Oct 2020 20:58:14 +0000 [thread overview]
Message-ID: <1E720961-55BD-4CC2-8F8F-E6324F900149@fb.com> (raw)
In-Reply-To: <SG2PR04MB30936F1769ABD503C232E6BEE1300@SG2PR04MB3093.apcprd04.prod.outlook.com>
On 10/1/20, 8:19 AM, "Jayashree D" <jayashree-d@hcl.com> wrote:
Classification: HCL Internal
Hi Team,
Currently there is no place holder to have all programmable elements versions. Whether any new repo can be created to maintain all the programmable versions in openbmc.
Kindly provide your suggestions to read all the firmware versions using OEM commands.
Whatever daemon is reading or collecting firmware version can create a PDI
version interface and add version there so it can be accessed by anyone who
needs it. Every version should be under PDI version interface, it makes easier
to make mapper call.
Regards,
Jayashree
prev parent reply other threads:[~2020-10-02 21:00 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
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 [this message]
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=1E720961-55BD-4CC2-8F8F-E6324F900149@fb.com \
--to=vijaykhemka@fb.com \
--cc=jayashree-d@hcl.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=velumanit@hcl.com \
--cc=yulei.sh@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).