commit | 6470582df6e248929ed42c3a7a6c68658da808fb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Jul 26 18:00:00 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 30 19:01:36 2021 +0000 |
tree | ec8727b110840b5cb9a802eed2448b98141f6b49 | |
parent | c7a0a0c5dcfc1d4de6abd4816f88315cacbd0de1 [diff] |
RAS Data file updates for PAU, NMMU, and PCI FIRs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I260bbeb3e3fe65f2af35f6645a240c29620dd997
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