Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 021dab3c73eab84d621500d8388392f85f73e4f3
commit021dab3c73eab84d621500d8388392f85f73e4f3[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Tue Dec 08 20:28:40 2020 -0600
committerZane Shelley <zshelle@us.ibm.com>Thu Dec 10 17:28:59 2020 +0000
tree4d226b1895e06381646648c51878463fe99b7bf4
parentbcf65a8b95ae1e2b9c9ea53fe749ceba625732ff [diff]
Add all signatures to PEL FFDC

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I5628c9ec7da34c7d9e023ac2e227de72b90626a9
1 file changed
tree: 4d226b1895e06381646648c51878463fe99b7bf4
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. cli.cpp
  9. cli.hpp
  10. LICENSE
  11. listener.cpp
  12. listener.hpp
  13. main.cpp
  14. main_nl.cpp
  15. MAINTAINERS
  16. meson.build
  17. meson_options.txt
  18. README.md
README.md

Hardware Diagnostics for POWER Systems

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.

Building

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