| commit | a6046a7b051c230b011122667cffd2a5bcd54012 | [log] [tgz] |
|---|---|---|
| author | Alexander Hansen <alexander.hansen@9elements.com> | Tue Nov 11 12:41:17 2025 +0100 |
| committer | Alexander Hansen <alexander.hansen@9elements.com> | Tue Nov 11 12:49:56 2025 +0100 |
| tree | 8db616c6efbf46bb6c8946c0bbe5aac63b0f2858 | |
| parent | b4c52ce6712625f18c54fc1994c847fbb5182c27 [diff] |
fix ci: move to stdexec::inline_scheduler
Move from `exec::inline_scheduler` to `stdexec::inline_scheduler`.
Looks like the definition has been deprecated and is pointing to
`stdexec::inline_scheduler` anyways.
the relevant header
```
namespace exec {
// A simple scheduler that executes its continuation inline, on the
// thread of the caller of start().
using inline_scheduler
[[deprecated("Use stdexec::inline_scheduler instead")]] = stdexec::inline_scheduler;
} // namespace exec
```
Tested: Inspection only.
Fixes: 10d0b4b7d1498cfd5c3d37edea271a54d1984e41
Change-Id: I1d23cb624e8902c541eeb31bd31155a3207a2da9
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
- platform-mc/sensor_manager.cpp[diff]
- platform-mc/terminus_manager.cpp[diff]
- requester/test/handler_test.cpp[diff]
- common/
- configurations/
- docs/
- fw-update/
- host-bmc/
- libpldmresponder/
- oem/
- platform-mc/
- pldmd/
- pldmtool/
- requester/
- softoff/
- subprojects/
- test/
- tools/
- utilities/
- .clang-format
- .clang-tidy
- .eslintignore
- .gitignore
- .linter-ignore
- LICENSE
- meson.build
- meson.options
- OWNERS
- README.md
PLDM - Platform Level Data Model
Overview
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.
Features
- Standardized Messaging: Adheres to the DMTF's PLDM specifications, enabling consistent and interoperable communication between different components.
- Modularity: Supports multiple PLDM types, including base, FRU,Firmware update, Platform Monitoring and Control, and BIOS Control and Configuration.
- Extensibility: Easily extendable to support new PLDM types and custom OEM commands.
- Integration: Seamlessly integrates with other OpenBMC components for comprehensive system management.
Getting Started
Prerequisites
To build and run PLDM, you need the following dependencies:
MesonNinja
Alternatively, source an OpenBMC ARM/x86 SDK.
Building
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
To run unit tests
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.
To enable pldm verbosity
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
To disable pldm verbosity
rm /etc/default/pldmd systemctl restart pldmd
Documentation
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.