commit | c18ba8fbf7a9d73952157a308c7d4b1418f3365a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 01 16:29:20 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 01 16:29:20 2021 -0600 |
tree | e2551249bd7cd3adfb50bea6581fbbc86677ada3 | |
parent | 5542ba38cb71a14ccb9146d07bf1abada405a781 [diff] |
Add Hostboot scratch registers to PEL Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I8f095b49ec204e6e33afc0ab300beeab5d3759a9
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