#
777cfaf2 |
| 13-Jun-2024 |
Johnathan Mantey <johnathanx.mantey@intel.com> |
Enable OEM creation of non-Type1 SDRs
Enabling the dbus-sdrs feature is useful for managing Type 1 SDR's using D-Bus. What doesn't work quite as well in the model is creating non-Type 1 records. The
Enable OEM creation of non-Type1 SDRs
Enabling the dbus-sdrs feature is useful for managing Type 1 SDR's using D-Bus. What doesn't work quite as well in the model is creating non-Type 1 records. The current method works alright for Type 11 FRU records. Any other SDR's beyond the FRU are problematic because the code depends on manually defining custom 'if' clauses to compare the incoming SDR ID, and determining what kind of SDR to create. It is a fixed process that is inflexible, and assumes every BMC vendor wants the same SDR arrangement.
This commit creates a model that allows the each OEM to customize creating each SDR using their own algorithm. The OEM creates a sensorcommands_oem.cpp/hpp file containing code for handling the creation of custom SDRs. The code here is compiled and linked based on enabling a Meson build switch.
The code follows the model that was already present in dbus-sdr/sensorcommands.cpp. There are two functions that maintain the original inflexible code, which is now expected to be primarily used as a template for the OEM cpp/hpp contents.
Tested: Created sensorcommands_oem.cpp/hpp files with OEM functionality Enabled the original code, and compiled Used ipmitool sdr dump sdrs.bin in the BMC Console Confirmed the SDRs matched the values prior to this commit. Enabled the OEM code and compiled Used ipmitool sdr dump sdrs.bin in the BMC console Confirmed the contents of the BIN file contained the SDRs generated by the sensorcommands_oem.cpp source.
Change-Id: I100e747b52677be53b499713d51c6c1126411570 Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>
show more ...
|
#
085de48d |
| 26-Sep-2023 |
Alexander Hansen <alexander.hansen@9elements.com> |
phosphor-sel-logger clears SEL
the SEL logger now clears the SEL and the option 'sel-logger-clears-sel' is removed.
This removes the ambiguity about who should clear it and provides a single implem
phosphor-sel-logger clears SEL
the SEL logger now clears the SEL and the option 'sel-logger-clears-sel' is removed.
This removes the ambiguity about who should clear it and provides a single implementation.
Tested: together with the other topic changes. SEL Add/Clear works.
Change-Id: I9d228ac418406272caf220170a824735108b5599 Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
show more ...
|
#
768730d2 |
| 06-Sep-2023 |
Patrick Williams <patrick@stwcx.xyz> |
meson: add option for open-power functions
This repository has long had an open-power only function that ends up compiled into all systems. We cannot use the phosphor-logging generated errors, unle
meson: add option for open-power functions
This repository has long had an open-power only function that ends up compiled into all systems. We cannot use the phosphor-logging generated errors, unless we are able to disable this code on non-open-power systems. Add necessary meson options.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Icd5b2f4cdec206597029930790ef2b10170d232a
show more ...
|
#
c2c26f93 |
| 17-Jul-2023 |
Alexander Hansen <alexander.hansen@9elements.com> |
multiple ipmi shortname implementations
As ipmi subsystem requires short names, and there are multiple ways to implement that, this patch provides compile-time configuration options.
- shortname-r
multiple ipmi shortname implementations
As ipmi subsystem requires short names, and there are multiple ways to implement that, this patch provides compile-time configuration options.
- shortname-remove-suffix - shortname-replace-words
Previously, PSU Sensor Names were stripped of some suffixes, some of which uniquely identified the sensor.
e.g. "_Input_Voltage", "_Output_Voltage". Without the suffix, the sensor cannot be uniquely identified.
Example: "PSU0_Input_Voltage", "PSU0_Output_Voltage" both become "PSU0".
Tested: - with both configurations turned off, name is only trucated - with nothing configured, default config is applied and suffix is removed (current behavior) - word replacement enabled and suffix removal disabled: expected behavior - word replacement disabled and suffix removal enabled: expected behavior
Change-Id: I01dd35f31e75df3c31733e9818884813a241440a Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
show more ...
|
#
ecffbaee |
| 15-Aug-2023 |
George Liu <liuxiwei@inspur.com> |
meson_options.txt: Support for reading options from meson.options
Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using t
meson_options.txt: Support for reading options from meson.options
Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts.
[1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I621a1d4139a00aa5044e586fbe1163b35563cad9
show more ...
|