Lines Matching +full:platform +full:- +full:specific
1 # PLDM - Platform Level Data Model
3 [](LICENSE)
7 PLDM (Platform Level Data Model) is a key component of the OpenBMC project,
8 providing a standardized data model and message formats for various platform
18 - **Standardized Messaging:** Adheres to the DMTF's PLDM specifications,
21 - **Modularity:** Supports multiple PLDM types, including base, FRU,Firmware
22 update, Platform Monitoring and Control, and BIOS Control and Configuration.
23 - **Extensibility:** Easily extendable to support new PLDM types and custom OEM
25 - **Integration:** Seamlessly integrates with other OpenBMC components for
34 - `Meson`
35 - `Ninja`
44 meson setup build && ninja -C build
52 meson setup builddir && meson setup test -C builddir
56 [these](https://github.com/openbmc/docs/blob/master/testing/local-ci-build.md)
61 pldm daemon accepts a command line argument `--verbose` or `--v` or `-v` to
66 echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd
79 At a high-level, code in this repository belongs to one of the following three
85 for a registration as well as a plug-in mechanism. The library is implemented in
86 modern C++, and handles OpenBMC's platform specifics.
97 #### OEM/vendor-specific functions
99 This will support OEM or vendor-specific functions and semantic information.
104 |---- oem
105 |----<oem_name>
106 |----libpldmresponder
107 |---<oem based handler files>
111 <oem_name> - This folder must be created with the name of the OEM/vendor in
123 For consistency would recommend using "oem-<oem_name>".
181 While PLDM Platform Descriptor Records (PDRs) are mostly static information,
182 they can vary across platforms and systems. For this reason, platform specific
183 PDR information is encoded in platform specific JSON files. JSON files must be
186 additional processing (apart from PDR creation) for specific PDR types, for eg
187 mapping an effecter id to a D-Bus object.
190 PDR repository. Platform specific PDR modifications would likely just result in
192 generation code. The PDR generator is a map of PDR Type -> C++ lambda to create
206 and type-specific metadata. PLDM parses
209 [Base BIOS Table](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_…
210 hosted by [BIOS Config Manager](https://github.com/openbmc/bios-settings-mgr).
212 [DesignDoc](https://github.com/openbmc/docs/blob/master/designs/remote-bios-configuration.md).
217 [Base BIOS Table](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_…
282 …cifies the character encoding format, which can be ASCII, Hex, UTF-8, UTF-16LE, or UTF-16BE. Curre…
295 system-specific BIOS attributes is crucial. To achieve this, BIOS JSON files are
298 [Compatible Interface](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/ope…
306 To enable system-specific BIOS attribute support within PLDM, the meson option
307 `system-specific-bios-json` can be utilized. With `system-specific-bios-json`
308 option `enabled` BIOS JSON files specific to the system type are fetched during