diff options
author | Vernon Mauery <vernon.mauery@linux.intel.com> | 2020-03-04 22:02:02 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-03-18 05:44:17 +0300 |
commit | e0b32cb26dd6a4a3ab04cf913d616ce2d5e7693c (patch) | |
tree | 4889e7e42a0880571564aee30c3b76c7e18b904c /meta-inspur | |
parent | 39f5a6b43b4ed43db5bf9b8eb8179a99c8533b62 (diff) | |
download | openbmc-e0b32cb26dd6a4a3ab04cf913d616ce2d5e7693c.tar.xz |
Update the ipmitool to a more recent commit
ipmitool is now under active development. This pulls in the latest
commit as of now.
Because of the change to a newer version of ipmitool, how it deals with
the enterprise-numbers file is different. Because the makefile just
wants to download the latest version (which would mean non-repeatable
builds), this commit manually downloads it so it is versioned.
I went through the list of companies that have CLAs with openBMC and
found them in the iana list. This mostly just means that if one of the
companies contributing to OpenBMC writes an OEM IPMI handler, ipmitool
will be able to determine what OEM it is by name. This is not an
essential thing in 99% of the cases. There won't be a need for any of
the iana numbers for any of the entities that are not writing IPMI OEM
providers.
This adds a note to the bbappend file to update the enterprise-numbers
file any time a new company joins the OpenBMC project by submitting a
CLA, assuming that they have a number on file with the IANA.
Tested: builds as expected. runs as expected from bmc console.
(From meta-phosphor rev: 0b4708bff38a85eb706f4ab4894c0aa584877633)
Change-Id: Id2cd25d693894805b79f8bd589246a135bd1490d
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-inspur')
0 files changed, 0 insertions, 0 deletions