Lines Matching +full:files +full:- +full:based
1 # PLDM - Platform Level Data Model
3 [](LICENSE)
18 - **Standardized Messaging:** Adheres to the DMTF's PLDM specifications,
21 - **Modularity:** Supports multiple PLDM types, including base, FRU,Firmware
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
94 Source files are named according to the PLDM Type, for eg base.[hpp/cpp],
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
115 Files having the oem functionality for the libpldmresponder library should be
123 For consistency would recommend using "oem-<oem_name>".
147 b) PLDM daemon routes message to message handler, based on the PLDM command.
166 several requester apps (based on functionality/PLDM remote device). Each of them
183 PDR information is encoded in platform specific JSON files. JSON files must be
184 named based on the PDR type number. For example a state effecter PDR JSON file
185 will be named 11.json. The JSON files may also include information to enable
187 mapping an effecter id to a D-Bus object.
189 The PLDM responder implementation finds and parses PDR JSON files to create the
192 generation code. The PDR generator is a map of PDR Type -> C++ lambda to create
193 PDR entries for that type based on the JSON, and to update the central PDR repo.
201 based on BIOS JSON files. BIOS functionality is integrated into PLDM according
203 [PLDM BIOS Specification](https://www.dmtf.org/sites/default/files/standards/documents/DSP0247_1.0.…
205 are structured within JSON files. Each attribute is defined by its name, type,
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_…
218 PLDM populates the Base BIOS Table for BIOS Config Manager based on BIOS Json
219 files.
221 After the JSON files are parsed, pldm would also create the string table,
223 [PLDM BIOS Specification](https://www.dmtf.org/sites/default/files/standards/documents/DSP0247_1.0.…
226 `bios attribute json files are kept under OEM`
232 [PLDM BIOS Specification](https://www.dmtf.org/sites/default/files/standards/documents/DSP0247_1.0.…
253 [PLDM BIOS Specification](https://www.dmtf.org/sites/default/files/standards/documents/DSP0247_1.0.…
274 [PLDM BIOS Specification](https://www.dmtf.org/sites/default/files/standards/documents/DSP0247_1.0.…
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