commit | 06e10f91faad6d3bc50c81670f9e100f8269a9d6 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 10 20:35:08 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 11 20:32:10 2020 +0000 |
tree | 8ad82091f410e5b73bfb451d60a91f2954545b01 | |
parent | 2f26318121b41f304b5ab6b738eb89087426b016 [diff] |
Get pib target for processor register access Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I4eeb4b7b79653724db67eaa881a5362072eef763
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