commit | ec8faedc27a6d57246c6ac0530d79e73c87abfd9 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Oct 22 17:39:30 2024 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Oct 22 17:39:30 2024 -0500 |
tree | 59ab74089ba10949993931e5f33c512f93e91454 | |
parent | 44d6f25ff8eb175afe5a29dd7986f2c98c73e499 [diff] |
updated OWNERS file Change-Id: Ibb397a6fd77507ea79644df2ab71600c5ab13077 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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