diff options
author | Abner Chang <abner.chang@hpe.com> | 2021-03-03 17:52:30 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2021-03-11 08:44:51 +0000 |
commit | 4751a48aeb2ab828b0a5cbdc585fd3642967cda1 (patch) | |
tree | ffef5dc51cf696dcddb547e0c14fe9554cba7f6e /OvmfPkg/Bhyve/PlatformPei | |
parent | 54ba08c6b66090bdc03186110149bfe4b0f75208 (diff) | |
download | edk2-4751a48aeb2ab828b0a5cbdc585fd3642967cda1.tar.gz edk2-4751a48aeb2ab828b0a5cbdc585fd3642967cda1.tar.bz2 edk2-4751a48aeb2ab828b0a5cbdc585fd3642967cda1.zip |
RedfishPkg/Library: RedfishLib
EDK2 port of DMTF libredfish project. We clone the necessary files
from open source project libredfish (https://github.com/DMTF/
libredfish) tag v1.0.0 and revise it to incorporate with edk2
firmware code base.
The reason of cloning the necessary files instead of using extern
submodule of libredfish project:
libredfish as a C library which is executed under Windows and
Linux. It could be binded with other programming languages such as
java and python. The library uses curl library as the communication service with Redfish, which is not easy to be abstracted and
replaced with EFI specific protocols (e.g. EFI_REST_EX_PROTOCOL or
payload encode/decode library) and EFI data types. We had the
conversation with DMTF community and they think edk2 is a firmware
solution but not the programming language,
therefore they rejected to have edk2 as a binding to libredfish.
According to above, we decide to clone the necessary files from
libredfish modify it to incorporate with edk2.
Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com>
Signed-off-by: Ting Ye <ting.ye@intel.com>
Signed-off-by: Siyuan Fu <siyuan.fu@intel.com>
Signed-off-by: Fan Wang <fan.wang@intel.com>
Signed-off-by: Abner Chang <abner.chang@hpe.com>
Cc: Nickle Wang <nickle.wang@hpe.com>
Reviewed-by: Nickle Wang <nickle.wang@hpe.com>
Diffstat (limited to 'OvmfPkg/Bhyve/PlatformPei')
0 files changed, 0 insertions, 0 deletions