commit | b99de182fa868d7adb07e95d4603706e31f84abd | [log] [tgz] |
---|---|---|
author | Johnathan Mantey <johnathanx.mantey@intel.com> | Thu Dec 21 08:28:18 2023 -0800 |
committer | Johnathan Mantey <johnathanx.mantey@intel.com> | Thu Feb 22 16:35:56 2024 +0000 |
tree | c40061a5c313be91f701b7db8153d2a3a87c6b1b | |
parent | f027bf0334b91de5c829d21082dd42b75b45a405 [diff] |
Assign ASCII-Latin8 to dbus-sdr FRU string Type/Len The FRU ID string Type/Len encoding in the dbus-sdr code is left unassigned, which causes it to be tagged as unicode characters. This is not the encoding of the data, which is actually ASCII/Latin8. The problem appears to go unnoticed, I expect, because the dbus-sdr functionality is not enabled. When dbus-sdr is enabled the id-string supplied to IPMITool is ASCII/Latin8, but IPMITool decodes it as unicode. Tested: Enabled dbus-sdr features. Use 'ipmitool fru print' Confirm FRU id-strings print as ASCII/Latin8 Change-Id: Ie6d936f6b5a0b0cd9ccd9adb68e46e1efbb9b2e5 Signed-off-by: Johnathan Mantey <johnathanx.mantey@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