commit | acd516bfd20318088e9194d76d961a1dd2bfa977 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jul 21 17:47:30 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 30 19:01:23 2021 +0000 |
tree | 0303fcb69547cff3b870fb3ed1d98f4915d75861 | |
parent | 90d125241e01583c37365c6394b537835b3f328d [diff] |
RAS data files for Explorer 1.1 and 2.0 Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: If9a7fa3a1fa31786079fb64e7a808a7bff8c0dcb
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