commit | f4bd5ff699132a919b0547738f7a1b0cc4f7b642 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Nov 05 22:26:04 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 02:23:10 2020 +0000 |
tree | a6e421eb0f74e8c727abb8a1683a2a647d312baf | |
parent | fb1905453908a6cfe0136bcf39b818e7e8ece225 [diff] |
Proper support for initializing the isolator Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id9a65dc6318420144a7ba9fb78d8a317f1181917
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