Searched full:dsp0248 (Results 1 – 21 of 21) sorted by relevance
19 Represents the type of the entity. See 9.2 in DSP0248 v1.2.0.23 Represents the instance number of the entity. See 9.3 in DSP024829 DSP0248 v1.2.0.
14 More information about PDR can be found at DSP0248 version 1.2.0 section 25.60 Multiple PDRs of the format present in table 89 of DSP024863 of DSP0248 of version 1.2.0 .107 Multiple PDRs of the format present in table 80 of DSP0248110 of DSP0248 of version 1.2.0 .
13 More information about PLDM Event Messages can be found at DSP0248 version20 More information about properties can be found at DSP0248 version
25 which is proposed to be added in a future version of DMTF [DSP0248].107 [DSP0248]: https://www.dmtf.org/dsp/DSP0248
431 DSP0248 1.2.1) or in the MCTP Entity-manager endpoint EID configuration file452 `Entity Association PDR` (section 28.17 of DSP0248 1.2.1).454 DSP0248 1.2.1).457 28.25, etc. of DSP0248 1.2.1).458 - The Fru info using FRU PDRs (section 28.22 of DSP0248 1.2.1).459 - The other info using the others PDRs in section 28.x of DSP0248 1.2.1.495 Regarding to the static device described in section 8.3.1 of DSP0248 1.2.1, the545 [DSP0248 1.2.1](https://www.dmtf.org/sites/default/files/standards/documents/DSP0248_1.2.1.pdf).
105 /** CPEREvent class (0x07) is only available in DSP0248 V1.3.0. in createOemEventHandler()106 * Before DSP0248 V1.3.0 spec, Ampere uses OEM event class 0xFA to in createOemEventHandler()
68 * per DSP0248. This data is memcpy'd.114 * @param[in/out] data - will point to PDR record data (as per DSP0248) on132 * @param[in/out] data - will point to PDR record data (as per DSP0248) on149 * @param[in] pdr_type - PDR type number as per DSP0248152 * @param[in/out] data - will point to PDR record data (as per DSP0248) on191 * whether the valid bit is set or not as per the spec DSP0248
130 * nameStringCount in `Table 95 - Entity Auxiliary Names PDR format` of DSP0248140 * FileNameLength in `Table 108 - File Descriptor PDR` of DSP0248 v1.3.0147 /* DSP0248 Table1 PLDM monitoring and control data types */160 * PLDM Platform and Control spec, DSP0248 v1.2.2. "If this value is445 /** @brief PLDM DSP0248 1.2.1 table 74 sensorUnits enumeration
34 /* EventClass sensorEvent `Table 11 - PLDM Event Types` DSP0248 */ in handlePlatformEvent()70 /* EventClass CPEREvent as `Table 11 - PLDM Event Types` DSP0248 V1.3.0 */ in handlePlatformEvent()76 /* EventClass pldmMessagePollEvent `Table 11 - PLDM Event Types` DSP0248 */ in handlePlatformEvent()
491 * format` DSP0248 V1.3.0 So the payload_length of `SetNumericEffecterValue` in setTerminusNumericEffecter()
115 // computation is based on table 79 from DSP0248 v1.1.1 in setStateEffecterStatesHandler()
410 // computation is based on table 79 from DSP0248 v1.1.1 in setStateEffecterStatesHandler()
146 * @param[in] sensorEventClass - sensor event class wrt DSP0248
191 * @param[in] sensorEventClass - sensor event class wrt DSP0248
74 /* DSP0248 section16.9 EventMessageBufferSize Command, the default message
117 * @param[in] eventDataFormat - format for PDRRepositoryChgEvent in DSP0248
261 example, for DSP0248 Platform Monitoring and Control, the symbol prefix
1981 // according to spec DSP0248 in parseResponseMsg()2199 // according to spec DSP0248 in parseResponseMsg()2202 // according to spec DSP0248 in parseResponseMsg()
271 id="tspan4676">DSP0248</tspan></text>
3382 * Note that the definition of nameLanguageTag in DSP0248 v1.2.2 in decode_pldm_entity_auxiliary_names_pdr_index()
