commit | 3a85108f9fdf27ca1e7e70469d4c327e0b19a00c | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 23 16:45:28 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 23 16:52:56 2021 -0500 |
tree | 61acb4870069ed87213d730d40148b74b8ca1c9e | |
parent | 0b8368cb0aa251032eb18b5c938d009e27f0b152 [diff] |
Config option to enable PHAL APIs There are a couple required PHAL APIs that are not available upstream. It is uncertain if these APIs will ever be available upstream. Fortunately, the APIs are only needed to provide information that is displayed in a PEL. So there is a less accuate alternative when the APIs are not available. Change-Id: I1a4a1838520c18053ab31f561d05875d4a94c20e Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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