commit | 317ccfec9e829ba10712742f1d546382eb2f1146 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jul 28 17:37:24 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 03 20:05:22 2021 +0000 |
tree | 2099a9b8cce8dae2f5b2d64cb92d76c8f09ad85e | |
parent | 42684b510c82be54701d7c3ca05335715b8c6268 [diff] |
RAS data file updates for TP_LOCAL_FIR Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie890d2d7c413c202d6bf6fcfb0ad060e85534d58
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