| commit | e693e21fc7c8ad8f13163dacc244f7865e0e100e | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@ieisystem.com> | Mon Aug 05 14:12:03 2024 +0800 |
| committer | George Liu <liuxiwei@ieisystem.com> | Tue Aug 06 08:43:51 2024 +0800 |
| tree | 539174aea64087905b2ebe8c15e78fc07a9a8ce3 | |
| parent | 394c77f059d2929b17cdcb13167652a27a543434 [diff] |
attn/Attention_Handler.md: Fix MD025 warnings The following warnings are generated by using markdownlint analysis: ``` attn/Attention_Handler.md:15 MD025/single-title/single-h1 Multiple top-level headings in the same document [Context: "# Overview"] attn/Attention_Handler.md:41 MD025/single-title/single-h1 Multiple top-level headings in the same document [Context: "# Implementation Details"] ``` Refer to markdown-lint [1] to fix MD025 [1]: https://github.com/updownpress/markdown-lint/blob/master/rules/025-single-h1.md Signed-off-by: George Liu <liuxiwei@ieisystem.com> Change-Id: I6cd05ec398eabf39f6f870a58103f22530f2cb3b
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.
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