commit | e13a9f95b0cd1756af2762493d45ea5104e68a30 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 16 21:19:11 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 16 21:19:11 2021 -0600 |
tree | d3f1674101d5da432ec63b40df9b5bae444f0bab | |
parent | 86aa97a50808e8358ac8582e2240c6ae50dd2ff1 [diff] |
created PluginResolution class Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I68560934b487f12b6b95dc73a93bb049f7777656
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