commit | 84721d9083afd9781834d69be33c3fb9a4559309 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Sep 08 13:30:27 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:24:07 2021 -0500 |
tree | 85fae7734fb182dc3af3da8405ca28e943592771 | |
parent | 74b40bf0499cc53c1b129971785a8c7dfcde8b56 [diff] |
Add support for clock callout resolutions Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I67f02a2fafaa63a0bafaa1116150da35ef4dece1
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
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