| commit | 34f902598235f9e5fb4e35b8c19c5e21c83e6cc9 | [log] [tgz] |
|---|---|---|
| author | Hoik Chen <hoik_chen@wiwynn.com> | Mon Oct 27 05:09:32 2025 +0000 |
| committer | Hoik Chen <hoik.chen.wiwynn@gmail.com> | Mon Oct 27 07:05:26 2025 +0000 |
| tree | 281c8fee9bfb1caf724dfe40dd37d703606a0245 | |
| parent | 6449a3b035f270b385ea213ab710bcdc3efc8f74 [diff] |
platform: Remove unnecessary auto Description: Remove the unnecessary auto to avoid using the wrong rc for ccOnlyResponse. Motivation: The response was using the rc variable defined outside the for loop, while the intended rc inside the loop was ignored. This caused incorrect return code to be sent during response handler. Change-Id: I89af3a7aced11b5c69415416c8c64a40fe5e6317 Signed-off-by: Hoik Chen <hoik.chen.wiwynn@gmail.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.