commit | c85716ca7532aded52285f91ce4741091f77cdb5 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 17 10:54:06 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 23 09:52:42 2021 -0500 |
tree | b1ebf579e9db4149f50f326acb565b5dbc7e9647 | |
parent | 7029e525adf8786bf374a51599a8938d6a8a3e48 [diff] |
Moved Callout class logic to Resolution classes This simplified the confusion between the Callout and Resolution classes because there was a lot of overlap. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iea0fb30a1577869ebfe5b2b195fee832a694adb5
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