| commit | f23fd543404a948ae436a5cf4092354dcb60a366 | [log] [tgz] |
|---|---|---|
| author | Archana Kakani <archanax.kakani@linux.intel.com> | Thu Sep 16 05:05:10 2021 +0000 |
| committer | AppaRao Puli <apparao.puli@linux.intel.com> | Thu Nov 25 06:03:25 2021 +0000 |
| tree | 76ecc496e5db0f9319a676fd177f9e97b485308c | |
| parent | 9e58cfe1ba5ca5bcd5263b50730c5a231eabdd4f [diff] |
StorageCmd: Get fru data from different services
Get fru details from fru interface defined under different services.
Removed hardcoded dependency with service and made it more generic
with respect to fru interface.
Tasks Completed:
1. Get the list of objectPaths and the services
implementing FruDevice Interface.
2. Get the details of all the object paths under
each service (ObjectPath->Interface->Properties)
3. Save only the objectpaths which have FruDevice interface.
4. Save the device id and corresponding objectPath.
5. In getFru,
Get Object path using device Id
Get service name using DBus query GetObject using object path
and "xyz.openbmc_project.FruDevice" interface.
Call GetRawFru using service name
Tested:
Used ipmitool fru command and observed that the Fru data is displayed
for all FRU's defined under different services.
Signed-off-by: Archana Kakani <archanax.kakani@linux.intel.com>
Change-Id: I389d4949e43ae95605b225e07aeb8e0e703c3454
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]