commit | a4134770850077cbe7171b8852a1fa1b3c1c6525 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Jan 10 17:22:44 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Jan 17 09:47:06 2022 -0600 |
tree | bdeea57b14856d0b09377b63905a21452d7b15ea | |
parent | 37acb2896f2341ba21e27cdb9960e0a265b5b537 [diff] |
Add support for PartCalloutResolution Change-Id: Ia9ab315e43d98a742d2ad88ba2fb33bd3e56ee86 Signed-off-by: Zane Shelley <zshelle@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