summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-phosphor/ipmi/ipmitool
AgeCommit message (Collapse)AuthorFilesLines
2020-03-18Update the ipmitool to a more recent commitVernon Mauery2-35/+113
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>
2019-04-25rebase ipmitool to use upstream gitVernon Mauery2-387/+35
Upstream ipmitool has been under active development for a while now. This includes adding the D-Bus interface to ipmitool as an option as well as a mechanism to set the default interface. So now, building ipmitool for openbmc is possible directly from upstream. The new patch that is included in this commit has been pushed upstream and in under review. It is needed to build in environments that don't have internet access. Tested-by: build ipmitool, run it on the BMC and see that it works bitbake ipmitool; scp <>/ipmitool <....>:/tmp; /tmp/ipmitool mc info /tmp/ipmitool -h ... Interfaces: open Linux OpenIPMI Interface imb Intel IMB Interface lan IPMI v1.5 LAN Interface lanplus IPMI v2.0 RMCP+ LAN Interface serial-terminal Serial Interface, Terminal Mode serial-basic Serial Interface, Basic Mode dbus OpenBMC D-Bus interface [default] (From meta-phosphor rev: c89d95e58d44d0f8e955892b59da2ac0c2beaf91) Change-Id: I00c15fb8693fca13cdd174661f924e7af684d19d Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-16phosphor: Move ipmitool fork to a set of patchesEd Tanous1-0/+387
Given that upstream yocto already has a recipe for ipmitool, it doesn't make sense for us to have a hard fork of it, especially when they are solving problems for us, and keep the version up to date. Functionally, this commit does 3 things. 1. Deletes the phosphor specific phosphor-ipmi-tool target 2. Adds the openbmc specific ipmitool patches into phosphor, for ease of updating to new versions in the future. 3. Updates ipmitool to the latest upstream version: 1.8.18 Tested By: Built an image with ipmitool included. Ran through some basic commands: ipmitool mc info ipmitool sensor list and observed no errors, and correct responses over dbus. Ran ipmitool --help and observed ipmitool version 1.8.18 in the output string. (From meta-phosphor rev: fe41c387618414906722b6a60b4c752cb6941d45) Change-Id: If1f0f3dbf8997576b8001e76318bbc231e8f59c0 Signed-off-by: Ed Tanous <ed.tanous@intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>