commit | 723fa239abb755460bac08cc37209a618c1e5cf1 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 09 12:02:06 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 16:29:07 2021 -0500 |
tree | fd7fbe73577de348c269d74158b2a5c3d5ecc921 | |
parent | ee54c99fb17e97a45e4398c8dd11f3d851c5ecff [diff] |
Replace LinkResolution with ResolutionList It's just easier to manage a list instead of chaining all the resolutions together. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I392fa49d2fe05d22ae82f7eed9cb120872904a08
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