commit | df9f8e4052fe31a59c0c15dbc6c4adbfd37cd2dc | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 18 12:19:08 2025 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Feb 19 19:15:14 2025 +0000 |
tree | fa3e88a60d38587035d03715bb9011c3f5d0a793 | |
parent | 316acdacb382ec27a6ede244e8fda3847db37fa7 [diff] |
Add xbus connections for new systems Change-Id: I4e36c21a872a4e480095656ccc189c88f6f609c6 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