commit | 548d1a27aa399392c00f9ad27c8990ecd047ca34 | [log] [tgz] |
---|---|---|
author | Sui Chen <suichen@google.com> | Wed Sep 14 07:41:17 2022 -0700 |
committer | Willy Tu <wltu@google.com> | Tue Sep 20 15:42:55 2022 +0000 |
tree | bb78f3425b8ef7eac79d09f00ada02dcd4ea9fb9 | |
parent | 902d90dacc33c762b44d25595d3be16c47bae444 [diff] |
dbus-sdr: write-back to fruCache upon modification ipmiStorageWriteFruData is a read-modify-write cycle: 1) Obtain a copy of the target FRU with getFru() 2) Modify the copy 3) Write modified copy FRU to EEPROM by calling `writeFru(fru)` or `writeFru(fruCache)`. For 3) above, whether `writeFru(fru)` or `writeFru(fruCache)` is called depends on the value of `atEnd`. Currently fruCacue is not updated in the atEnd==false branch, where `writeFru(fruCache)` is called. This may cause the unmodified FRU content to be written back, as if the write did not happen. This change adds the write-back operation. Tested: FRU write works Signed-off-by: Sui Chen <suichen@google.com> Change-Id: Idfe76c97a3117289ebf2d98abfecc4c7b8f05ea1
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