commit | a68302797149f0ed37920a5a9fe9e78039d899e3 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Mon Jun 12 16:05:58 2023 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Mon Jun 12 16:07:04 2023 -0500 |
tree | 072b369c10b58acc0f4047ba26d6bfc44fe4561c | |
parent | bdb8667c351f22c461b4184603b4b03fe01085a8 [diff] |
Minor updates for RAS data json for Odyssey Change-Id: I2872c7d6a5d90090b73819f450c190e998ac1761 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