commit | bc94bdea8543a92d3f41074cd177da78c4028202 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Feb 18 09:03:37 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 21 19:35:41 2022 +0000 |
tree | 37d5c6d82289bb445ae49beaa201d82a45d1cd96 | |
parent | 444fa1c0249320eb734150156534c0283942fe1a [diff] |
Add NX target and update target to subsystem map Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Id55834370343748ecddfa6d23f70747d75708593
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