| commit | 316acdacb382ec27a6ede244e8fda3847db37fa7 | [log] [tgz] |
|---|---|---|
| author | Pavithra Barithaya <pavithrabarithaya07@gmail.com> | Mon Jan 20 14:57:12 2025 +0530 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 18 12:58:34 2025 -0600 |
| tree | e4a044acbf99a404606a2c07ea9ab284d9ee144d | |
| parent | 9b1a0b6b0e9e6018cd820e259e39516da1c2d826 [diff] |
Add kernel MCTP (AF_MCTP) support and transport-implementation option -Added support for kernel MCTP (AF_MCTP) to enable MCTP communication using AF_MCTP sockets. - Introduced a new configuration option 'transport-implementation' The 'transport-implementation' option can be set to either: - 'mctp-demux': Uses the existing mctp-demux transport method. - 'af-mctp': Uses the new kernel AF_MCTP transport method. Change-Id: Ib2f7b97d0a96ceaa0cb0fc8cd7313e84c03bbd61 Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>
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