Google Git Google Git
Sign in
gbmc/pldm/58355cc7592be9250e43753cae16f66f0b8be519
commit
58355cc7592be9250e43753cae16f66f0b8be519
[log]
author
Alex Lai <alexlai@google.com>
Thu Oct 08 01:10:59 2026 +0000
committer
Alex Lai <alexlai@google.com>
Mon Oct 12 04:43:56 2026 +0000
tree
e14b3cdf39df06f6cfbb367a829f20f15556e864
parent
10e55a76dd65fff5c6723c58121408de616de3bc [diff] 
platform-mc: Use Terminus_<NID>_<EID> as default terminus name

When an MCTP endpoint does not have a target Name from mctpreactor (or the
name is empty), set its default terminus name to
Terminus_<NetworkId>_<EID> instead of falling back to Terminus_<TID>. This
gives endpoints with static (NetworkId, EID) assignments a deterministic
name independent of PLDM discovery order, while dynamic endpoints managed
by mctpreactor continue to use their configured Name.

Name precedence is otherwise unchanged:
PDR Entity Auxiliary Name > mctpreactor Name > Terminus_<NID>_<EID>.

Note: Endpoints without an mctpreactor Name or PDR Entity Auxiliary Name
are renamed from Terminus_<TID> to Terminus_<NID>_<EID>, which changes
their inventory/sensor D-Bus object paths and Redfish IDs.

Change-Id: I6adc95c86cb8909fcc148be6c89b10f317838577
Signed-off-by: Alex Lai <alexlai@google.com>
2 files changed
tree: e14b3cdf39df06f6cfbb367a829f20f15556e864
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. fw-update-legacy/
  6. host-bmc/
  7. libpldmresponder/
  8. oem/
  9. platform-mc/
  10. pldmd/
  11. pldmtool/
  12. requester/
  13. softoff/
  14. subprojects/
  15. test/
  16. tools/
  17. utilities/
  18. .clang-format
  19. .clang-tidy
  20. .eslintignore
  21. .gitignore
  22. .linter-ignore
  23. LICENSE
  24. meson.build
  25. meson.options
  26. OWNERS
  27. README.md
README.md

PLDM - Platform Level Data Model

License

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:

  • Meson
  • Ninja

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.