commit | ff4982a2b2cfd96e1bbb2f9e80fa224bbc3b99dd | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Tue Oct 04 17:27:35 2022 -0700 |
committer | Vernon Mauery <vernon.mauery@linux.intel.com> | Mon Oct 17 22:58:07 2022 +0000 |
tree | 3ea1667ee15949180e42e1de736f4f944e8a53af | |
parent | 097497fb7b2466e85d2800991bef92017b044cda [diff] |
Move the location of sensor object manager Per phosphor-dbus-interfaces, all sensor implementations should be implementing an ObjectManager at /xyz/openbmc_project/sensors This commit updates intel-ipmi-oem to look from the corrrect location. Tested: No good way to test, as I don't have an intel-ipmi-oem platform, but a similar patch made to phosphor-ipmi-host showed the correct results. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I6d059cb1da79a7444da813e329b7ed7ebd8d0350
This component is intended to provide Intel-specific IPMI[3]
command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.
intel-ipmi-oem
serves as an extension[1]
to OpenBMC IPMI daemon[2]
. It is compiled as a shared library and intended to both:
Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:
[4]