commit | 6eb619035ae8a57d8e532b23d8bc1966eb032f7d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri May 15 22:25:58 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Sat May 16 10:18:23 2020 -0500 |
tree | 241898253f82fc72c7a666c409ab6508e991e71e | |
parent | d0659241dc96f934486d108c73aa43565d905e9a [diff] |
Add capture regs from Chip Data File to IsolationNode Change-Id: Ia91821f2b14e12ed917c97b622789710ffb8bdb4 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
This library is a common, portable code base for isolating errors reported by hardware registers on POWER Systems chips.
The primary consumers (and requirements drivers) will be:
See the primary API definitions for details on how to use this library.
This library can be integrated into a user application's source (either imported, or as a git subtree/submodule) or built as static library.
__HEI_ENABLE_HW_WRITE
: When defined, it will allow hardware write support. Note that the Chip Data Files will contain rules for clearing and masking register bits. Both of which will require modifying hardware registers, which is not allowed by user applications like OpenBMC or FSP firmware.src/include/
in the POWER Systems Hostboot firmware.For a standard OpenBMC release build, you want something like:
meson setup -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson setup -Dtests=enabled <build_dir> meson test -C <build_dir>