commit | 0fe5df40e48815be7ef305f9eee57f897627e0aa | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Dec 03 08:57:17 2020 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Thu Dec 03 20:04:19 2020 +0000 |
tree | e1809eef396bfc06e929ac09e969c1876b7c4b54 | |
parent | 5adc96eed9197c08bfaf66b4e204b3d519917f08 [diff] |
Attn: Add TI info command field to valid check Added an additional check of command == 0xa1 in the TI info data area to determine if the TI info data has been populated. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I3f8c43c4fdcb086acb66d235c9b53712d21b58c1
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