From: "Nickle Wang" <nicklew@nvidia.com>
To: <devel@edk2.groups.io>
Cc: Abner Chang <abner.chang@amd.com>,
Igor Kulchytskyy <igork@ami.com>,
"Nick Ramirez" <nramirez@nvidia.com>
Subject: [edk2-staging][PATCH 0/3] Introduce resource addendum protocol
Date: Wed, 7 Dec 2022 22:40:15 +0800 [thread overview]
Message-ID: <20221207144015.266-1-nicklew@nvidia.com> (raw)
Introduce EDKII_REDFISH_RESOURCE_ADDENDUM_PROTOCOL to Redfish feature driver.
Feature driver uses this protocol to query OEM resource from platform in
order to support Redfish OEM property. This protocol is also used to get
addendum data that is required by BMC to manage Redfish BIOS service.
Signed-off-by: Nickle Wang <nicklew@nvidia.com>
Cc: Abner Chang <abner.chang@amd.com>
Cc: Igor Kulchytskyy <igork@ami.com>
Cc: Nick Ramirez <nramirez@nvidia.com>
Nickle Wang (3):
edk2-staging/RedfishClientPkg: Add Redfish Resource Addendum Protocol
edk2-staging/RedfishClientPkg: Add Redfish Resource Addendum Library
edk2-staging/RedfishClientPkg: Utilize RedfishAddendumLib
.../Features/Bios/v1_0_9/Common/BiosCommon.c | 100 +++++++
.../Features/Bios/v1_0_9/Dxe/BiosDxe.inf | 2 +
.../Include/Library/RedfishAddendumLib.h | 63 +++++
.../EdkIIRedfishResourceAddendumProtocol.h | 77 ++++++
.../Include/RedfishResourceCommon.h | 2 +
.../RedfishAddendumLib/RedfishAddendumLib.c | 258 ++++++++++++++++++
.../RedfishAddendumLib/RedfishAddendumLib.inf | 40 +++
RedfishClientPkg/RedfishClientLibs.dsc.inc | 2 +
RedfishClientPkg/RedfishClientPkg.dec | 2 +
9 files changed, 546 insertions(+)
create mode 100644 RedfishClientPkg/Include/Library/RedfishAddendumLib.h
create mode 100644 RedfishClientPkg/Include/Protocol/EdkIIRedfishResourceAddendumProtocol.h
create mode 100644 RedfishClientPkg/Library/RedfishAddendumLib/RedfishAddendumLib.c
create mode 100644 RedfishClientPkg/Library/RedfishAddendumLib/RedfishAddendumLib.inf
--
2.38.1.windows.1
reply other threads:[~2022-12-07 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221207144015.266-1-nicklew@nvidia.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox