commit | 324234b4b560ce1d136d96a6950daeb1da1469a5 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Jun 28 17:01:17 2021 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Mon Jun 28 17:01:17 2021 -0500 |
tree | 36d6d74c29f530152531ddd8a098ba44d731c5e7 | |
parent | b1eda6a3cbb9b7c6a2c46a4550a7cce396467ee0 [diff] |
Util: Add common dbus code to util namespace Add dbus code that can be used by analyzer, isolator, attention to util. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I6205ea227b72c7bafa230446c3c2120b87abc207
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