commit | 5d63cefcada92a8588ab55fb2a741c898cb19a8b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 17 18:10:17 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:42:34 2021 -0500 |
tree | 9670664c75ccf23cc1020ef410e829fc12e2b587 | |
parent | 96d5486c3ca5c5037e6f74bd3a1d196d91b80829 [diff] |
ConnectedCalloutResolution support Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id1b215d70ca98ae18528f91162ff4d99de9e9ce8
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