commit | 46b456bd75731b9046b48485dcac00993d6e648e | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Jul 07 12:30:08 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Jul 13 16:16:05 2020 +0000 |
tree | 293036de123ee89ff820e2af6c736dc134265d12 | |
parent | b797b3e1852f5fb59d65b9ebe787aabbbd2b8462 [diff] |
Do not qualify active attentions with true-mask We were using cfam 0x100d to qualify active attentions as valid reasons for invocation of the attention handler. This is not needed as the attention handler will only be invoked by a GPIO event which should only occur when 0x100d is configured correclty. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I7814ab9f3b4a79801d8f66f75589dd5722a7c4d2
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