commit | e550061ea1df23abb6fd175aab4749b3e2e6e3a8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Oct 27 09:46:05 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Oct 27 09:46:05 2021 -0500 |
tree | 6d16e4d6a43f834b3493ec66996fedbcca9d06d4 | |
parent | d94291aa2f3248cd829b29a91caa137b24aea5e1 [diff] |
update OWNERS file Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: If65859f03f8b0bcd3393ba10dd07765bef2102cf
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