commit | ae60d8e4e79ae456843297dd754f1003e72232bd | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Aug 28 16:09:20 2024 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Aug 30 13:34:28 2024 +0000 |
tree | 37ea49d81f64bc7343583a7d8ffa1c2647d12987 | |
parent | 8db65db6333e5b38d1aa19dc94bbca9e5424ffed [diff] |
Add chip_config user option to chip_data/setup.py Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: I69784a74feb95c36e91c59a610d04b1fcfe4f0f6
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 -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test