commit | 1d881b57baad59a4e143c780b49a90a59bad2915 | [log] [tgz] |
---|---|---|
author | Jitendra Tripathy <jitendra.kumarx.tripathy@intel.com> | Fri May 16 10:08:15 2025 +0000 |
committer | Jitendra Tripathy <jitendra.kumarx.tripathy@intel.com> | Wed Jun 04 09:50:35 2025 +0000 |
tree | 843f82203843ba3f06ce8e2d1dd9bddaf1f70a4e | |
parent | 20862ea0f2960a99103d4ffcfc1fbf30bd49d1f1 [diff] |
Fix IPMI FRU Device Description display string Resolved an issue where the IPMI command "ipmitool fru list" did not display proper human-readable string values for the "Fru Device Description" field for certain FRUs. The problem occurred because the current code retrieves the value for the "Fru Device Description" field from the "PRODUCT_PRODUCT_NAME" property, which might simply having dots or dashes if the FRU entity is not qualified to call it as PRODUCT. To address this, the priority has been changed to the unique "BOARD_PRODUCT_NAME" property, as "PRODUCT_PRODUCT_NAME" could also be shared by multiple Board FRU entities sharing the product. If the "BOARD_PRODUCT_NAME" property is unavailable, the value will still be retrieved from "PRODUCT_PRODUCT_NAME". Tested: Verified using ipmitool fru list Change-Id: Iea91844f2b15d19f58b15b979d830adaf5f17c6a Signed-off-by: Jitendra Tripathy <jitendra.kumarx.tripathy@intel.com>
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in ipmid/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja -C builddir test ninja -C builddir coverage