<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Hello,<br>
<br>
We have an implementation of this command <a
href="https://github.com/openbmc/phosphor-host-ipmid/blob/master/apphandler.cpp#L571">https://github.com/openbmc/phosphor-host-ipmid/blob/master/apphandler.cpp#L571</a>
. 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 <a
href="https://github.com/openbmc/openbmc/blob/master/meta-ibm/recipes-phosphor/ipmi/phosphor-ipmi-config.bbappend">https://github.com/openbmc/openbmc/blob/master/meta-ibm/recipes-phosphor/ipmi/phosphor-ipmi-config.bbappend</a>.<br>
<br>
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 <a
href="https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/33893">https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/33893.</a>
<p>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.<br>
<br>
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? <br>
<br>
Is a common code possible for converting arbitrary tag formats to
IPMI firmware revision fields?<br>
</p>
Regards,<br>
Tom<br>
<p><br>
</p>
</body>
</html>