| commit | 8042a3eb3526b52c19b3f19810177dfa2a90856c | [log] [tgz] |
|---|---|---|
| author | Swaroop Aradhya N M <swaroopx.aradhya.n.m@intel.com> | Fri Feb 13 09:30:27 2026 +0000 |
| committer | Swaroop Aradhya N M <swaroopx.aradhya.n.m@intel.com> | Fri Feb 13 09:58:15 2026 +0000 |
| tree | aa7f4d8afae371458c8a9229e3803081e8de9e78 | |
| parent | 653dc5891408186a7001c6f38c4ecc538b409f87 [diff] |
Fix chassis intrusion D-Bus path and enum handling The chassis intrusion IPMI command was returning 0xCC (Invalid Data Field) due to incorrect D-Bus object path and enum string handling. The handler was using wrong path "/xyz/openbmc_project/Intrusion/Chassis_Intrusion" and comparing against short enum strings instead of full returned string. Update the D-Bus path to "/xyz/openbmc_project/Chassis/Intrusion" and fix enum comparisons to use complete qualified enum strings. Tested: IPMI command now returns success with correct chassis intrusion status. Change-Id: Icb3b776bc62c61a6b8db0d940cccd2d0db07f1e8 Signed-off-by: Utkarsh Kumar <utkarshx.kumar@intel.com> Signed-off-by: Swaroop Aradhya N M <swaroopx.aradhya.n.m@intel.com>
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]