commit | 30984d1574cb4154c625f0925afcd76e65b984e8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 22 17:17:54 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 29 18:18:54 2022 +0000 |
tree | 093d1b9a5d0489753ac4c2f73de2945e5fbdf369 | |
parent | dd779995caa24b654da52fac79bae08a4d1474c3 [diff] |
Support to use lg2 logging Change-Id: I3a11433fa6bbbad165a65037b9253eda7206f946
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