* Read Firmware Versions @ 2020-09-21 14:12 Jayashree D 2020-09-21 15:23 ` Patrick Williams 0 siblings, 1 reply; 12+ messages in thread From: Jayashree D @ 2020-09-21 14:12 UTC (permalink / raw) To: openbmc; +Cc: Velumani T-ERS,HCLTech [-- Attachment #1: Type: text/plain, Size: 1690 bytes --] Classification: HCL Internal Hi Team, 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). Regards, Jayashree ::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. ________________________________ [-- Attachment #2: Type: text/html, Size: 4312 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 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 0 siblings, 2 replies; 12+ messages in thread From: Patrick Williams @ 2020-09-21 15:23 UTC (permalink / raw) To: Jayashree D; +Cc: openbmc, Velumani T-ERS, HCLTech [-- 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 --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-09-21 15:23 ` Patrick Williams @ 2020-09-21 15:23 ` Patrick Williams 2020-09-22 13:34 ` Jayashree D 1 sibling, 0 replies; 12+ messages in thread From: Patrick Williams @ 2020-09-21 15:23 UTC (permalink / raw) To: Jayashree D; +Cc: openbmc, Velumani T-ERS,HCLTech [-- 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 --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Read Firmware Versions 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 1 sibling, 2 replies; 12+ messages in thread From: Jayashree D @ 2020-09-22 13:34 UTC (permalink / raw) To: Patrick Williams, openbmc; +Cc: Velumani T-ERS,HCLTech 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. ________________________________ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-09-22 13:34 ` Jayashree D @ 2020-09-22 20:52 ` Vijay Khemka 2020-09-23 15:35 ` Patrick Williams 1 sibling, 0 replies; 12+ messages in thread From: Vijay Khemka @ 2020-09-22 20:52 UTC (permalink / raw) To: Jayashree D, Patrick Williams, openbmc; +Cc: Velumani T-ERS,HCLTech On 9/22/20, 6:37 AM, "openbmc on behalf of Jayashree D" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of jayashree-d@hcl.com> 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. Those oem command needs to read firmware version from dbus interface if there are any exposed. I am not sure how much we are exposing firmware version currently. 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. ________________________________ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 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 1 sibling, 1 reply; 12+ messages in thread From: Patrick Williams @ 2020-09-23 15:35 UTC (permalink / raw) To: Jayashree D; +Cc: openbmc, Velumani T-ERS, HCLTech [-- 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 --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-09-23 15:35 ` Patrick Williams @ 2020-09-23 20:17 ` Adriana Kobylak 2020-09-24 1:39 ` Vijay Khemka 0 siblings, 1 reply; 12+ messages in thread From: Adriana Kobylak @ 2020-09-23 20:17 UTC (permalink / raw) To: Patrick Williams; +Cc: Velumani T-ERS, HCLTech, openbmc, Jayashree D, openbmc On 2020-09-23 10:35, Patrick Williams wrote: > 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? It could fit in phosphor-bmc-code-mgmt, some thoughts: The d-bus objects get created at 2 different times: 1. One scenario is when an image is uploaded to be updated, this is the support that Vijay added which allows a custom script to be run to update the BIOS image. If you're interested in this method for updating your BIOS, you could potentially add your IPMB commands in that service and use the Activation interfaces to drive the update. 2. The second scenario is when the BMC reboots and it recreates the d-bus objects. For this scenario, there's no currently support for BIOS, so for example the support that Vijay added does not create a d-bus interface if the BMC reboots, which is ok if you only want to use the Activation interface to trigger the update. But sounds like you want to always have the version information as a d-bus object, so support for BIOS could be added. For example, to get the BMC levels, the code looks for version information in the BMC in the media directory. If you get your app to get the version information via the oem commands you mentioned and create a file in the bmc in the media directory we could extend the logic to create the Version d-bus objects for each BIOS version when the BMC reboots. We'd just need to work out the details for the format for the files that would host the version information, and how to identify they're BIOS versions vs BMC. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-09-23 20:17 ` Adriana Kobylak @ 2020-09-24 1:39 ` Vijay Khemka 2020-09-24 2:36 ` Lei Yu 0 siblings, 1 reply; 12+ messages in thread From: Vijay Khemka @ 2020-09-24 1:39 UTC (permalink / raw) To: Adriana Kobylak, Patrick Williams Cc: Jayashree D, openbmc, Velumani T-ERS, HCLTech, openbmc On 9/23/20, 1:19 PM, "openbmc on behalf of Adriana Kobylak" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of anoo@linux.ibm.com> wrote: On 2020-09-23 10:35, Patrick Williams wrote: > 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? It could fit in phosphor-bmc-code-mgmt, some thoughts: The d-bus objects get created at 2 different times: 1. One scenario is when an image is uploaded to be updated, this is the support that Vijay added which allows a custom script to be run to update the BIOS image. If you're interested in this method for updating your BIOS, you could potentially add your IPMB commands in that service and use the Activation interfaces to drive the update. 2. The second scenario is when the BMC reboots and it recreates the d-bus objects. For this scenario, there's no currently support for BIOS, so for example the support that Vijay added does not create a d-bus interface if the BMC reboots, which is ok if you only want to use the Activation interface to trigger the update. But sounds like you want to always have the version information as a d-bus object, so support for BIOS could be added. For example, to get the BMC levels, the code looks for version information in the BMC in the media directory. If you get your app to get the version information via the oem commands you mentioned and create a file in the bmc in the media directory we could extend the logic to create the Version d-bus objects for each BIOS version when the BMC reboots. We'd just need to work out the details for the format for the files that would host the version information, and how to identify they're BIOS versions vs BMC. I already create a file after reading bios version via oem commands, Is there a pattern where should we keep this file and what is the name of file. Also I thought there is a dbus interface for bios management already created by some daemon newly added which can keep bios version. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-09-24 1:39 ` Vijay Khemka @ 2020-09-24 2:36 ` Lei Yu 2020-09-25 11:49 ` Jayashree D 0 siblings, 1 reply; 12+ messages in thread From: Lei Yu @ 2020-09-24 2:36 UTC (permalink / raw) To: Vijay Khemka; +Cc: openbmc, Jayashree D, openbmc, Velumani T-ERS, HCLTech On Thu, Sep 24, 2020 at 9:40 AM Vijay Khemka <vijaykhemka@fb.com> wrote: > > > > On 9/23/20, 1:19 PM, "openbmc on behalf of Adriana Kobylak" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of anoo@linux.ibm.com> wrote: > > On 2020-09-23 10:35, Patrick Williams wrote: > > 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? > > It could fit in phosphor-bmc-code-mgmt, some thoughts: > > The d-bus objects get created at 2 different times: > > 1. One scenario is when an image is uploaded to be updated, this is the > support that Vijay added which allows a custom script to be run to > update the BIOS image. If you're interested in this method for updating > your BIOS, you could potentially add your IPMB commands in that service > and use the Activation interfaces to drive the update. > > 2. The second scenario is when the BMC reboots and it recreates the > d-bus objects. For this scenario, there's no currently support for BIOS, > so for example the support that Vijay added does not create a d-bus > interface if the BMC reboots, which is ok if you only want to use the > Activation interface to trigger the update. But sounds like you want to > always have the version information as a d-bus object, so support for > BIOS could be added. For example, to get the BMC levels, the code looks > for version information in the BMC in the media directory. If you get > your app to get the version information via the oem commands you > mentioned and create a file in the bmc in the media directory we could > extend the logic to create the Version d-bus objects for each BIOS > version when the BMC reboots. We'd just need to work out the details for > the format for the files that would host the version information, and > how to identify they're BIOS versions vs BMC. > > I already create a file after reading bios version via oem commands, Is there > a pattern where should we keep this file and what is the name of file. Also > I thought there is a dbus interface for bios management already created by > some daemon newly added which can keep bios version. > We plan to do something like this: 1. The BIOS version is stored in an eeprom; 2. On BMC boot, phosphor-bmc-code-mgmt creates the bios object, and fill the version read from the eeprom; 3. When the host is started, BIOS sends its version via OEM ipmi command; 4. BMC will update and write the version to the eeprom if the version is different. -- BRs, Lei YU ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Read Firmware Versions 2020-09-24 2:36 ` Lei Yu @ 2020-09-25 11:49 ` Jayashree D 2020-10-01 15:19 ` Jayashree D 0 siblings, 1 reply; 12+ messages in thread From: Jayashree D @ 2020-09-25 11:49 UTC (permalink / raw) To: openbmc; +Cc: Lei Yu, openbmc, Velumani T-ERS, HCLTech, Vijay Khemka Classification: HCL Internal On Thu, Sep 24, 2020 at 9:40 AM Vijay Khemka <vijaykhemka@fb.com> wrote: > > > > On 9/23/20, 1:19 PM, "openbmc on behalf of Adriana Kobylak" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of anoo@linux.ibm.com> wrote: > > On 2020-09-23 10:35, Patrick Williams wrote: > > 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? > > It could fit in phosphor-bmc-code-mgmt, some thoughts: > > The d-bus objects get created at 2 different times: > > 1. One scenario is when an image is uploaded to be updated, this is the > support that Vijay added which allows a custom script to be run to > update the BIOS image. If you're interested in this method for updating > your BIOS, you could potentially add your IPMB commands in that service > and use the Activation interfaces to drive the update. > > 2. The second scenario is when the BMC reboots and it recreates the > d-bus objects. For this scenario, there's no currently support for BIOS, > so for example the support that Vijay added does not create a d-bus > interface if the BMC reboots, which is ok if you only want to use the > Activation interface to trigger the update. But sounds like you want to > always have the version information as a d-bus object, so support for > BIOS could be added. For example, to get the BMC levels, the code looks > for version information in the BMC in the media directory. If you get > your app to get the version information via the oem commands you > mentioned and create a file in the bmc in the media directory we could > extend the logic to create the Version d-bus objects for each BIOS > version when the BMC reboots. We'd just need to work out the details for > the format for the files that would host the version information, and > how to identify they're BIOS versions vs BMC. > > I already create a file after reading bios version via oem commands, > Is there a pattern where should we keep this file and what is the name > of file. Also I thought there is a dbus interface for bios management > already created by some daemon newly added which can keep bios version. > >We plan to do something like this: >1. The BIOS version is stored in an eeprom; 2. On BMC boot, phosphor-bmc-code-mgmt creates the bios object, and fill the version read >from the eeprom; 3. When the host is started, BIOS sends its version via OEM ipmi command; 4. BMC will update and write the version to >the eeprom if the version is different. I understand that currently there is no separate repo to deal with all the firmware versions (ME, CPLD, VR, Bridge IC, BIOS). Whether any new repo can be created to place all programmable versions in openbmc. Or is there any way to read all the firmware versions from any other repo using oem commands Kindly provide your comments on this. Regards, Jayashree ::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. ________________________________ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Read Firmware Versions 2020-09-25 11:49 ` Jayashree D @ 2020-10-01 15:19 ` Jayashree D 2020-10-02 20:58 ` Vijay Khemka 0 siblings, 1 reply; 12+ messages in thread From: Jayashree D @ 2020-10-01 15:19 UTC (permalink / raw) To: openbmc; +Cc: Lei Yu, openbmc, Velumani T-ERS, HCLTech, Vijay Khemka 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. Regards, Jayashree -----Original Message----- From: Jayashree D Sent: Friday, September 25, 2020 5:20 PM To: openbmc@lists.ozlabs.org Cc: Adriana Kobylak <anoo@linux.ibm.com>; Patrick Williams <patrick@stwcx.xyz>; Velumani T-ERS,HCLTech <velumanit@hcl.com>; openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>; Vijay Khemka <vijaykhemka@fb.com>; Lei Yu <yulei.sh@bytedance.com> Subject: RE: Read Firmware Versions Classification: HCL Internal On Thu, Sep 24, 2020 at 9:40 AM Vijay Khemka <vijaykhemka@fb.com> wrote: > > > > On 9/23/20, 1:19 PM, "openbmc on behalf of Adriana Kobylak" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of anoo@linux.ibm.com> wrote: > > On 2020-09-23 10:35, Patrick Williams wrote: > > 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? > > It could fit in phosphor-bmc-code-mgmt, some thoughts: > > The d-bus objects get created at 2 different times: > > 1. One scenario is when an image is uploaded to be updated, this is the > support that Vijay added which allows a custom script to be run to > update the BIOS image. If you're interested in this method for updating > your BIOS, you could potentially add your IPMB commands in that service > and use the Activation interfaces to drive the update. > > 2. The second scenario is when the BMC reboots and it recreates the > d-bus objects. For this scenario, there's no currently support for BIOS, > so for example the support that Vijay added does not create a d-bus > interface if the BMC reboots, which is ok if you only want to use the > Activation interface to trigger the update. But sounds like you want to > always have the version information as a d-bus object, so support for > BIOS could be added. For example, to get the BMC levels, the code looks > for version information in the BMC in the media directory. If you get > your app to get the version information via the oem commands you > mentioned and create a file in the bmc in the media directory we could > extend the logic to create the Version d-bus objects for each BIOS > version when the BMC reboots. We'd just need to work out the details for > the format for the files that would host the version information, and > how to identify they're BIOS versions vs BMC. > > I already create a file after reading bios version via oem commands, > Is there a pattern where should we keep this file and what is the name > of file. Also I thought there is a dbus interface for bios management > already created by some daemon newly added which can keep bios version. > >We plan to do something like this: >1. The BIOS version is stored in an eeprom; 2. On BMC boot, phosphor-bmc-code-mgmt creates the bios object, and fill the version read >from the eeprom; 3. When the host is started, BIOS sends its version via OEM ipmi command; 4. BMC will update and write the version to >the eeprom if the version is different. I understand that currently there is no separate repo to deal with all the firmware versions (ME, CPLD, VR, Bridge IC, BIOS). Whether any new repo can be created to place all programmable versions in openbmc. Or is there any way to read all the firmware versions from any other repo using oem commands Kindly provide your comments on this. Regards, Jayashree ::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. ________________________________ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Read Firmware Versions 2020-10-01 15:19 ` Jayashree D @ 2020-10-02 20:58 ` Vijay Khemka 0 siblings, 0 replies; 12+ messages in thread From: Vijay Khemka @ 2020-10-02 20:58 UTC (permalink / raw) To: Jayashree D, openbmc; +Cc: Lei Yu, Velumani T-ERS, HCLTech, openbmc 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2020-10-02 21:00 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 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).