commit | 734185ae719eca8e184ef2759323023e371bd393 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 24 17:11:31 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 24 17:11:31 2021 -0500 |
tree | 29a3593d634feef049de6f6bb45ca4e40f803315 | |
parent | 340708d65e8e2c0cb21b19588ebefc9df73a1a42 [diff] |
Update action files for all chiplet local FIRs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia9fef3dc535b762e323a47fe52b270524dfa588d
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