openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jayashree D <jayashree-d@hcl.com>
To: Patrick Williams <patrick@stwcx.xyz>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Velumani T-ERS,HCLTech" <velumanit@hcl.com>
Subject: RE: Read Firmware Versions
Date: Tue, 22 Sep 2020 13:34:50 +0000	[thread overview]
Message-ID: <SG2PR04MB3093A25A217B7E1FFD65D8A8E13B0@SG2PR04MB3093.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <20200921152337.GJ6152@heinlein>

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?

Regards,
Jayashree

-----Original Message-----
From: Patrick Williams <patrick@stwcx.xyz>
Sent: Monday, September 21, 2020 8:54 PM
To: Jayashree D <jayashree-d@hcl.com>
Cc: openbmc@lists.ozlabs.org; Velumani T-ERS,HCLTech <velumanit@hcl.com>
Subject: Re: Read Firmware Versions

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
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

  parent reply	other threads:[~2020-09-22 13:37 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 [this message]
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=SG2PR04MB3093A25A217B7E1FFD65D8A8E13B0@SG2PR04MB3093.apcprd04.prod.outlook.com \
    --to=jayashree-d@hcl.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --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).