commit | 78f1c8944506e829ea0de7993a5750c66220f0ca | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Sep 23 16:14:47 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Sep 23 16:14:47 2021 -0500 |
tree | 228ab22a6c697f12d1e5ada649b873c3c1d1141f | |
parent | 4757a7bc1fbdf283686f29246eb2c36bdbfea40e [diff] |
Update action for all chiplet and global FIRs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I25571119575ffcb3c1a155359ee77037003c6dc7
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