summaryrefslogtreecommitdiffstats
path: root/meta-aspeed/recipes-kernel
diff options
context:
space:
mode:
authorEd Tanous <ed.tanous@intel.com>2019-01-11 16:26:13 -0800
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2019-01-16 13:18:21 +0000
commitd9aea6f7c72edf25c674caeee6bd9f4043c919a8 (patch)
tree31dc9868e1b30831abf8662f124e24a626de5669 /meta-aspeed/recipes-kernel
parent6b8d479ae1016f5df9aca37b3e6c78d32558d287 (diff)
downloadtalos-openbmc-d9aea6f7c72edf25c674caeee6bd9f4043c919a8.tar.gz
talos-openbmc-d9aea6f7c72edf25c674caeee6bd9f4043c919a8.zip
phosphor: Move ipmitool fork to a set of patches
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>
Diffstat (limited to 'meta-aspeed/recipes-kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud