commit | e0b10c8fea31fbf84158c67f629b3edda495fba9 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Thu Apr 04 09:30:18 2024 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Thu Apr 04 12:07:35 2024 -0500 |
tree | 39eddd01c34088e823e5a38795990a91dc172b4e | |
parent | b1ef8c42c7464c1df26652e74973ddea4fcc76ed [diff] |
RAS data file PAU_FIR updates Change-Id: I69841a57fb3782d8acdb13ab66c4feeb01d2847f Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
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