commit | 5542ba38cb71a14ccb9146d07bf1abada405a781 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 29 14:51:04 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 29 14:51:04 2021 -0600 |
tree | 35810bce03eba324c41d09179e3e16f959f6556f | |
parent | 04f010abb7946c18d6bb68c714ca6a4417845d8d [diff] |
Fix MCC target paths in P10 RAS data files Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I2b36a314b310398b817e719f1ab3062d585ca45a
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