commit | 2467db800aa8414561ebbf1e1ff14098eac54cab | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon May 18 19:56:30 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed May 20 15:33:45 2020 -0500 |
tree | 6f8993172fb917eaa8c2f619769086855c86a7e8 | |
parent | f229d5f93bb287d503c06b920a2f5d2b7aaac041 [diff] |
Add root nodes from Chip Data File to IsolationChip Change-Id: I3e49e784517ce2deca201955aa10d0a3d3fc0dfb 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>