Replies: 1 comment
-
RedfishConfigHandlerDriver will normally be dispatched by DXE dispatcher when all dependencies are satisfied. If we like to load it manually, we have to handle dependency on ourselves. The dependency for RedfishConfigHandlerDriver can be found in INF file: edk2/RedfishPkg/RedfishConfigHandler/RedfishConfigHandlerDriver.inf Lines 58 to 60 in c1dd400 It requires Redfish Credential Protocol to be ready and functional. This is the way that Redfish driver can get the credential and talk to BMC. You can check here for the architecture design of Redfish driver stack: https://github.com/tianocore/edk2/blob/master/RedfishPkg/Readme.md#edk2-redfish-implementation-diagrams |
Beta Was this translation helpful? Give feedback.
-
Hey,
I'm currently developing my first UEFI application, and it needs to communicate to a Redfish API.
I'm compiling the RedfishPkg using:
After successfully compiling this produces some efi files in ./Build/RedfishPkg/RELEASE_GCC5/X64
But when I try to load the confighandler in the UEFI shell, provided by OVMF, I get this error:
My qemu logs contains the following messages:
Because I'm really inexperienced in EDK2 I have no clue how to debug this issue, and how to correctly load and use the RedfishPkg. Any pointers would be greatly appreciated!
Thanks,
Timo
Beta Was this translation helpful? Give feedback.
All reactions