commit | 6b2a5a4e15e54ffd155fab69b6aa775a58b4f5cc | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 26 15:33:30 2024 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Apr 04 19:36:59 2024 +0000 |
tree | 0228aac21365ad5fca136b11bb52817d5717ecff | |
parent | e0b10c8fea31fbf84158c67f629b3edda495fba9 [diff] |
Updating OWNERS file Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia9dc59e811f3cb2897d0baaace485dbd9455d1e0
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