HII and Redfish on Host Adapters

Hi,

Just a followup to this post. I performed some additional experiments for this issue and, while I haven't yet figured out what the issue is, maybe someone will have some insight into what I'm seeing.

The first thing I wanted to confirm was whether the reason data was not showing up under Redfish was because I was loading the sample driver too late in the boot process. To confirm this, I changed some of our HII settings to flag that they were REST_STYLE, as well as added the "x-UEFI-ns" language to them, which is what the sample details. These changes were built into our Option ROM driver so they automatically load on system boot. However, this did not change the behavior on the system and our parameters still do not show up under $(IP)/redfish/v1/Systems/1/Bios (or anywhere else I searched for). Is possible that these settings are pushed to the BMC before any Option ROM drivers are loaded?

To confirm that I was building these settings correctly, I created a sample application that used the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL to query parameters in the system by their namespaces. I could see tons of settings in the "x-UEFI" namespace, and the couple that I've presented in the "x-UEFI-ns" namespace. I even see some onboard Option ROM settings (like an Onboard NIC) that show up using the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL and show up under some /Oem attribute area in the Redfish output (not under the expected System/1/Bios area). However, no matter what I've done I can't see to get any of our settings to show up in the Redfish output. I even changed our namespace to "x-UEFI" as a test, but that didn't do anything.

Does anyone have any experience with this? Is this something that System Firmware will do on a case-by-case basis, based on what is expected on the system?

I plan on trying a wider variety of platforms to see if this is consistent behavior, but I wanted to make sure what I was doing made sense in the first place.


Thank you for any insight into this.