commit | 89c0a7af33236c1963be6fe5673d7134fbb71555 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Aug 07 12:07:35 2020 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Aug 07 12:07:35 2020 -0500 |
tree | 74d81ceddcc0c82c2eae5064807db655f5a1d0b2 | |
parent | 46b456bd75731b9046b48485dcac00993d6e648e [diff] |
Use pib target for sbe_mpipl_get_ti_info call Attention handler was incorrectly using the fsi target for the call to sbe_mpipl_get_ti_info. Changed code to use a pib target. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I037508accf24d562c7dc8f04a25d4d245f9fc2eb
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