commit | 1eff945ee1d20f7fe0a3e36525ad63f83226737c | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 03 13:59:54 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 03 17:47:19 2021 -0500 |
tree | 666a9ba38e3939064952d7d05533c2967abde0f2 | |
parent | a06dcf82ba0c118f14d92ec800e38c188e73a1f7 [diff] |
Updates to ClockCalloutResolution behavior For P10, there are no plans to support clock targets in the device tree. So the resolution is to simply callout the backplane and not support to guard the clock targets. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ife77d3631ad6c0760d99778c70efffb28af1db12
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