commit | d195b7163dfe3dc54147932c4227c188d1076916 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 26 13:26:34 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 26 13:26:34 2022 -0600 |
tree | 5a8b48c58d353b8326babd99ff188623dd10c6d8 | |
parent | cbd20fa3ef069f5b34013d177a5468e37a83b77e [diff] |
Add support for TOD clock callouts Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I42726f6d1b036120fcfe217e6dd47be8dd6d927b
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