commit | 5e622d870609b79b9a210596a42e4a110f210d99 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Sep 11 10:10:24 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Sep 16 02:51:12 2020 +0000 |
tree | f791ec6dc09fc62b24dc792d16decf7ae428d3f2 | |
parent | 9fb7393efc60449fba06b1cc0f18152abd57c31a [diff] |
ATTN: Find FSI target by proc path Instead of iterating over class "fsi" we now iterate over class "proc" and find the FSI target by path and processor association. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: If011ac62a32e3de18feea86c57cd8bbb5f50b724
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