commit | 407177256644d60572d639826db03c2ab2cc8ee6 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Sep 23 09:43:20 2020 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Thu Sep 24 10:11:50 2020 -0500 |
tree | 8cd30e4d1127163cd37a91fa36761482fa056bc1 | |
parent | ff17f96364a2e80d3c804b7cfa87bc07138a8cf1 [diff] |
ATTN:ti_handler Add TI data to PEL Parse TI data buffer and store in PEL. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I5baf4c14719f510281c2943ea681c6db53c9c87e
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