commit | d26298b1204afb31ffdb0386679b4eeb89b7b9d5 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Jan 28 16:49:19 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 02 16:06:35 2021 -0600 |
tree | 8e70e85ffdc218157df50d8e75dca21edd032315 | |
parent | dc5b0ff1d62ffbf232bde9753d1c071e2ff64069 [diff] |
Generic binary file stream support (big-endian) Change-Id: I27bd490103fd193e35b0bbda17f7a1c90b566ecc 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