Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / d6af0b1c23568905589293df240568199ce90d9d
commitd6af0b1c23568905589293df240568199ce90d9d[log] [tgz]
authoraustinfcui <austinfcui@gmail.com>Fri Oct 29 14:55:37 2021 -0500
committerZane Shelley <zshelle@us.ibm.com>Tue Nov 02 19:17:50 2021 +0000
tree319381495168db8c0db0d2c03a22beb84234d641
parentf4792d68505ca033ac01ff42b806d9d7569cf7ff [diff]
Update discord info in OWNERS file

Signed-off-by: austinfcui <austinfcui@gmail.com>
Change-Id: I8d3db38f30a7ad27400600cc62cc133eac690fd6
1 file changed
tree: 319381495168db8c0db0d2c03a22beb84234d641
  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