Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 4414c517f449824a5501f5fd04a90a0ac66710e2
commit4414c517f449824a5501f5fd04a90a0ac66710e2[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Wed May 03 14:49:40 2023 -0600
committerZane Shelley <zshelle@us.ibm.com>Mon May 15 21:52:29 2023 +0000
treeb405805bb64e01dd01e8b2c6bab64fff9e8eafd3
parent27dd6368d4e6b1fd03610503356f24eb08a16c02 [diff]
remove OSStart as indication host is running

This function is checking whether PHYP is at standby or runtime. The
OSStart was never implemented by PHYP so it should not be looked at to
determine this state. The hostboot team is going to utilize this
BootProgress to indicate when they are starting PHYP.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieeaf69c812b54d00ce23d4e872a9e68a33439e0c
1 file changed
tree: b405805bb64e01dd01e8b2c6bab64fff9e8eafd3
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. .prettierignore
  10. .prettierrc.yaml
  11. buildinfo.hpp.in
  12. cli.cpp
  13. cli.hpp
  14. config.h.in
  15. LICENSE
  16. listener.cpp
  17. listener.hpp
  18. main.cpp
  19. main_nl.cpp
  20. meson.build
  21. meson_options.txt
  22. OWNERS
  23. 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