commit | be619c009af31265e30431cfaa43c0f8dd0322a6 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Sep 30 17:56:42 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Sun Oct 03 09:22:54 2021 -0500 |
tree | e649e3db0f5704acfca10e23629243a7fb1bb0ab | |
parent | 7de01130957b899128c8f413d585118e6db4115f [diff] |
RAS file updates for PAUC chiplet Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id46de43f2aa69b1f838b196aa3e1ddbad5ed00e6
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