| commit | fc5c80ee4111870abcd3bb2982d1b1a2ba07b4ec | [log] [tgz] |
|---|---|---|
| author | Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> | Fri Oct 18 07:07:46 2024 +0000 |
| committer | Vernon Mauery <vernon.mauery@linux.intel.com> | Tue Oct 22 19:57:58 2024 +0000 |
| tree | 40be420ac5e4f914c813cfcd03570f290a5d1efa | |
| parent | ab5c0e5763a6e25c7d44758b5522a5d4e0cb6728 [diff] |
Fix for Change in LED Controller service Due to below upstream change, user unable to Set SM Signal for different LED's. All the dbus calls also affected due to this change. https://gerrit.openbmc.org/c/openbmc/phosphor-led-sysfs/+/57455 Currently all LED Controllers are grouped into single service. So this fix provides to support for all the LED controllers based on new service i.e. xyz.openbmc_project.LED.Controller Tested: Ipmitool commands are verified working as expected. Command: ipmitool raw 0x30 0xb4 0x03 0x02 //Set Security mode Response: //Success Command: ipmitool raw 0x30 0x15 0x0D 00 00 00 //Set SM Signal Response: //Success Signed-off-by: Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> Change-Id: I4ee6f0d3f6148aae69e04fde028ab8ec46187ad8
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]