IPMI implementation of Get Device ID command

TOM JOSEPH tomjose at linux.vnet.ibm.com
Sat Aug 15 03:34:45 AEST 2020


Hello,

We have an implementation of this command 
https://github.com/openbmc/phosphor-host-ipmid/blob/master/apphandler.cpp#L571 
. The current version of the code derives the major and minor firmware 
revision from the VERSION_ID field, and the auxiliary firmware revision 
is picked from dev_id.json. The auxiliary firmware revision is populated 
at build time 
https://github.com/openbmc/openbmc/blob/master/meta-ibm/recipes-phosphor/ipmi/phosphor-ipmi-config.bbappend.

The implementation of the code is obsolete, as it was based on an 
earlier format. The current format of VERSION_ID for example is, 
2.9.0-dev-609-g56f86d23c. There is already a WIP patch to fix this for 
the master tag format 
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/33893. 
<https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/33893>

IBM tagging format is different from the tag format of master builds. 
One choice is to have the major and minor version added to the 
dev_id.json and if the format of VERSION_ID does not match the master 
tag format,  pick from the json.

How are other companies converting their arbitrary tag formats to IPMI 
firmware revision fields? Does every company maintain their own 
downstream implementation of this command?

Is a common code possible for converting arbitrary tag formats to IPMI 
firmware revision fields?

Regards,
Tom


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200814/62f3b746/attachment-0001.htm>


More information about the openbmc mailing list