commit | 35257fd2fbaea4562cdd937ad60b1d8a4c9ed9af | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Thu Dec 09 17:56:00 2021 -0600 |
committer | Austin Cui <austinfcui@gmail.com> | Fri Jan 21 04:21:11 2022 +0000 |
tree | 5c4642bab978ae6ad874e02874f5680579169662 | |
parent | e90b85dc659b2a8224fd6a52110460e36277ba6d [diff] |
Add pdbg test cases to use test device tree file. Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: I9a82bb954e0a329691579a10fdf7e71c229d1e73
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