commit | 5ea83fad72af5389c215c5da45c6342c63e9557f | [log] [tgz] |
---|---|---|
author | Thang Tran <thuutran@amperecomputing.com> | Mon Oct 16 14:37:56 2023 +0700 |
committer | Thang Tran <thuutran@amperecomputing.com> | Mon Oct 16 15:15:36 2023 +0700 |
tree | 6152c4629e934826912ceb41a67c5c69767c180b | |
parent | 4fc7b69ec4cabe9e9fd20ea6f038e37493118de5 [diff] |
dcmi: fix Get Sensor Info command Issue: if users request to Get Sensors Info via "ipmitool dcmi sensors" command, the Record ID of sensors always are 0x0000. Root Cause: In the loop of scanning the configuration file to get the record ID, it is using the "config" variable instead of the "reading" variable. It makes the record ID always is 0x0000. Solution: Replace the "config" variable with the "reading" variable. Tested: 1. Request to Get Sensors Info. $ipmitool dcmi sensors 2. The list of sensors and temperature are shown. Change-Id: If2b03b6b8a077a4e9239403ec9ecd640f645cbc0 Signed-off-by: Thang Tran <thuutran@amperecomputing.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