commit | 15527a43fe309d3599d146d5a48607b14b426a37 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 16 21:43:13 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Dec 17 18:17:32 2021 +0000 |
tree | f5a5d52e7316ce51317f817b41f5006f3d06baba | |
parent | e13a9f95b0cd1756af2762493d45ea5104e68a30 [diff] |
create PluginMap and plugin definition Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I1d4c9c59657f7c07f0fffdd6dc94d5d21033ff0a
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