commit | ee54c99fb17e97a45e4398c8dd11f3d851c5ecff | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Sun Aug 08 17:46:48 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 16:25:55 2021 -0500 |
tree | 66a1f74fa724f6819ed3075e8414c60470f978a0 | |
parent | a9b443442d16f836c08931e1b53deb5a1784d692 [diff] |
Add versioning to RAS data schemas Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie1688f748fe70d40bee4c88160cb20b7d36d3033
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