transport: specialize throw message per transport backend Specialize the error message per transport backend so consumers can quickly identify which transport layer failed to initialize. Without this change, a generic "Cannot initialize transport layer" error is thrown regardless of which transport backend pldmd was built with. Consumers have no way to distinguish whether the issue is a missing mctp-demux service, a missing af-mctp service, or pldmd being built with the wrong transport support. Change-Id: I003785f05c7c492c040fa4df4a46bdf59a087081 Signed-off-by: Vishnunithyasoundhar S <vishnunithyasoundhar.s@intel.com>
PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.
The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
The simplest way of running the tests is as described by the meson man page:
meson test -C build
Alternatively, tests can be run in the OpenBMC CI docker container using these steps.
pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.
echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd systemctl restart pldmd
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.