commit | afc6acda80df62cc0d288467419dd9b1307a8b40 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 12 14:32:56 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 12 14:38:34 2022 -0600 |
tree | e6dd4babd8fa9966b71a264630842645d0c1a76f | |
parent | 2923775f8356cc58e93a3e8d5d70958253de3808 [diff] |
add custom pdbg devtree for testing Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I7da81c1e45f4f5cec433684bf90a85910155718b
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