commit | 55e7fec3b6fc836749ad5f57b6213074ce29324b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Jan 28 15:29:44 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Feb 04 17:45:23 2022 +0000 |
tree | 77d1408b14c0f133cfa0f9302624280873e83ee0 | |
parent | 76e52f6d8808e15f44c84a28e623cfed89654b5d [diff] |
Update primary SRC field based on callout list Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I41f3eda5c27b8ec74d6329b8f145181f400547f8
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