commit | b9a8e762209bf43d13fac6955860df0642d815b3 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon May 11 21:41:32 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu May 14 18:49:04 2020 +0000 |
tree | 6a9f6cd2e41cfd10c91a2a997618044527a639e8 | |
parent | 4caa043734b83f96a843139f61a621dffb9ef732 [diff] |
Build HardwareRegister objects from Chip Data Files Change-Id: I4fbcdd5ba012008000b8d1f324dd47d95ef2d932 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>