Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / a06dcf82ba0c118f14d92ec800e38c188e73a1f7
commita06dcf82ba0c118f14d92ec800e38c188e73a1f7[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Wed Nov 03 10:23:21 2021 -0500
committerZane Shelley <zshelle@us.ibm.com>Wed Nov 03 11:25:33 2021 -0500
treed417e7e1b9bccb98cf70d3e83d3e1f88f81ea224
parent39fcf65dce4d91601951c146a543bf85d68f6b3c [diff]
include config header for use of CONFIG_PHAL_API

CONFIG_PHAL_API is defined in config.h, which was not included in
attn_handler.cpp before use of CONFIG_PHAL_API.

Change-Id: Ic5fb0695bc0811ffcd232511b52023e33469c43a
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
1 file changed
tree: d417e7e1b9bccb98cf70d3e83d3e1f88f81ea224
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. buildinfo.hpp.in
  9. cli.cpp
  10. cli.hpp
  11. config.h.in
  12. LICENSE
  13. listener.cpp
  14. listener.hpp
  15. main.cpp
  16. main_nl.cpp
  17. MAINTAINERS
  18. meson.build
  19. meson_options.txt
  20. OWNERS
  21. 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