Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 506db4c8dfd0b67f8516d1cb8e3c01b2074aea2e
commit506db4c8dfd0b67f8516d1cb8e3c01b2074aea2e[log] [tgz]
authorGeorge Liu <liuxiwei@ieisystem.com>Mon Aug 05 14:13:43 2024 +0800
committerGeorge Liu <liuxiwei@ieisystem.com>Tue Aug 06 08:43:51 2024 +0800
tree0cd80298adaa48696cc1875f7681ae8eb72d1e87
parente693e21fc7c8ad8f13163dacc244f7865e0e100e [diff]
analyzer/ras-data/ras-data-definition.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I7bcddf15b7b059a0be181c09fec4924f2d15ecb8
1 file changed
tree: 0cd80298adaa48696cc1875f7681ae8eb72d1e87
  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
  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