commit | 2a394cbb19cbc909e82736aa5a21172a19ae001a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 17 22:01:39 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 21 13:37:04 2022 -0600 |
tree | 6befeb32550324c70120df61d842a6d849160675 | |
parent | 8794bf861a0cdbc6b6e5b9de0029ac91c4c59ccb [diff] |
pdbg util to get chip/unit target from unit/chip Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia5c72c5667b7f6eb1ecb02c044dca5208a211c70
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