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: Mon, 21 Sep 2020 10:23:37 -0500 [thread overview]
Message-ID: <20200921152337.GJ6152@heinlein> (raw)
Message-ID: <20200921152337.2w6bmaq0EccmeTPWG0bNnN9vtAKK7d7G27XCYqm-SQI@z> (raw)
In-Reply-To: <SG2PR04MB3093CAA5913439BB892C16E5E13A0@SG2PR04MB3093.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Mon, Sep 21, 2020 at 02:12:55PM +0000, Jayashree D wrote:
> We are working on a platform which has multi host and each host have firmware versions such as CPLD, ME, BIOS, Bridge IC and VR.
> We have to display it in dbus objects.
> Can you please provide your comments on which dbus objects it will be suitable to store all firmware versions.
>
> Also in phosphor-dbus-interfaces, I am seeing "System.interface.yaml" in /xyz/openbmc_project/Inventory/Item/.
> Whether it will be suitable to store all the firmware versions (/xyz/openbmc_project/Inventory/Item/System/HostN).
All software versions should be modelled per [1]. The sub-section [2]
tells how to associate an inventory object to a software version (to
show which BIOS version a specific host card is running for example).
I don't think 'Inventory.Item.System' is intended to represent a single
host in a multi-host system; 'System' would represent the entire
chassis. You may want to use 'Chassis' or 'Board' to model a
sub-assembly.
1. https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Software
2. https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Software#find-all-software-versions-on-a-managed-element
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-21 15:23 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 [this message]
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
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=20200921152337.GJ6152@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 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).