commit | 4757a7bc1fbdf283686f29246eb2c36bdbfea40e | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:23:38 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:49:30 2021 -0500 |
tree | 91ea9bb955581a09d40218c37af8c96cb3c4d92b | |
parent | 979e2871f3fd78cf68ba9e2c325c2ae784a7d8b4 [diff] |
Bus callout resolution support Change-Id: I516d151350ac0d2342c966266f2e90bae8572c37 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