commit | 48f8a4183d6707d6ba0eacb444e5fbc38c940dda | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Oct 04 21:48:30 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Oct 05 10:21:51 2021 -0500 |
tree | 035f56858428bc62cf7045a54d96c5b3788cfb8e | |
parent | 1298240660292791c862d86a25c5efd7d0181ac4 [diff] |
RAS data file updates for MC chiplet Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I9356b6db825f106ddf02ab9ee0562b1781c9ea52
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