oem-meta: drop host-requested sled-wide power control The power control command let a host ask for a sled cycle or a NIC power cycle. Both act on hardware the requester shares with other hosts, and the request says nothing about whether the sender may do that, so the handler has no way to tell one request from another. Remove both. What is left, the 12V and DC slot cycles, acts on the slot derived from the sender's TID, so a host can still cycle itself. Tested: builds clean. Not exercised on hardware. Change-Id: I44e5256c179f2a0ad25471e632be0483aabd3c8b Signed-off-by: Pete O_o <pmb@meta.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.