* [PATCH] RedfishPkg: update Readme.md
@ 2023-06-05 14:41 Nickle Wang
2023-06-07 1:34 ` Chang, Abner
0 siblings, 1 reply; 2+ messages in thread
From: Nickle Wang @ 2023-06-05 14:41 UTC (permalink / raw)
To: devel; +Cc: Abner Chang, Igor Kulchytskyy
RedfishClientPkg is moved from edk2-staging repository to
edk2-redfish-client repository. Update the link in Readme.md
to new location.
Signed-off-by: Nickle Wang <nicklew@nvidia.com>
Cc: Abner Chang <abner.chang@amd.com>
Cc: Igor Kulchytskyy <igork@ami.com>
---
RedfishPkg/Readme.md | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/RedfishPkg/Readme.md b/RedfishPkg/Readme.md
index 7defe78eb1e0..3156c89f027d 100644
--- a/RedfishPkg/Readme.md
+++ b/RedfishPkg/Readme.md
@@ -5,7 +5,7 @@ UEFI Redfish EDK2 solution is an efficient and secure solution for the end-users
Below are the block diagrams of UEFI Redfish EDK2 Implementation. ***[EDK2 Redfish Foundation[1]](#[0])*** in the lower part of the figure refers to the EDK2 Redfish Foundation, which provides the fundamental EDK2 drivers to communicate with Redfish service ***([[19]](#[0]) in the above figure)***. The Redfish service could be implemented in BMC to manage the system, or on the network for managing multiple systems.
-***[EDK2 Redfish Client[2]](#[0])*** in the upper part of the figure refers to the EDK2 Redfish client, which is the EDK2 Redfish application used to configure platform configurations by consuming the Redfish properties. The EDK2 Redfish client can also provision the UEFI platform-owned Redfish properties, consume and update Redfish properties as well. The ***[EDK2 Redfish Feature DXE Drivers [17]](https://github.com/tianocore/edk2-staging/blob/edk2-redfish-client/RedfishClientPkg/Readme.md)*** is the project under development in EDK2 staging repository. Each EDK2 Redfish Feature DXE Driver is designed to communicate with the particular Redfish data model defined in the Redfish schema *(e.g. Edk2RedfishBiosDxe driver manipulates the properties defined in Redfish BIOS data model)*.
+***[EDK2 Redfish Client[2]](#[0])*** in the upper part of the figure refers to the EDK2 Redfish client, which is the EDK2 Redfish application used to configure platform configurations by consuming the Redfish properties. The EDK2 Redfish client can also provision the UEFI platform-owned Redfish properties, consume and update Redfish properties as well. The ***[EDK2 Redfish Feature DXE Drivers [17]](https://github.com/tianocore/edk2-redfish-client/blob/main/RedfishClientPkg/Readme.md)*** is the project in tianocore/edk2-redfish-client repository. Each EDK2 Redfish Feature DXE Driver is designed to communicate with the particular Redfish data model defined in the Redfish schema *(e.g. Edk2RedfishBiosDxe driver manipulates the properties defined in Redfish BIOS data model)*.
## <a name="[0]">EDK2 Redfish Implementation Diagrams</a>
@@ -136,16 +136,16 @@ programmatic way to recognize the BMC-exposed USB NIC.
The USB NIC exposed by BMC must be reported as one of the message channels as 802.3 LAN/IPMB 1.0 message
channel.
- | IPMI NetFn | IPMI Command| Purpose | Corresponding Host Interface Field|
- |------------|-------------|---------|-----------------------------------|
- | App<br>(0x06) | 0x42 | Check the message channel's medium type and protocol.<br>Medium: 802.3 LAN<br>Protocol: IPMB 1.0| None|
- | Transport<br>(0x0C) | 0x02 | Get MAC address of message channel. Used to match with the MAC address populated in EFI Device Path of network device| None|
- | Group Ext<br>(0x2C) | Group Extension ID: 0x52<br>Command: 0x02 | Check if Redfish bootstrap credential is supported or not.| In Device Descriptor Data, Credential Bootstrapping Handle|
- | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x04 | Get BMC-end message channel IP address source| In Protocol Specific Record Data<br>- Host IP Assignment Type<br>- Redfish Service IP Discovery Type<br>- Generate the Host-side IP address|.
- | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x03 | Get BMC-end message channel IPv4 address| In Protocol Specific Record Data<br>- Host IP Address Format<br>- Host IP Address|
- | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x06 | Get BMC-end message channel IPv4 subnet mask| In Protocol Specific Record Data<br>- Host IP Mask<br>- Redfish Service IP Mask|
- | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x12 | Get BMC-end message channel gateway IP address| None, used to configure edk2 network configuration|
- | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x14 | Get BMC-end message channel VLAN ID| In Protocol Specific Record Data<br> Redfish Service VLAN ID|
+ | IPMI NetFn | IPMI Command | Purpose | Corresponding Host Interface Field |
+ | ------------------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+ | App<br>(0x06) | 0x42 | Check the message channel's medium type and protocol.<br>Medium: 802.3 LAN<br>Protocol: IPMB 1.0 | None |
+ | Transport<br>(0x0C) | 0x02 | Get MAC address of message channel. Used to match with the MAC address populated in EFI Device Path of network device | None |
+ | Group Ext<br>(0x2C) | Group Extension ID: 0x52<br>Command: 0x02 | Check if Redfish bootstrap credential is supported or not. | In Device Descriptor Data, Credential Bootstrapping Handle |
+ | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x04 | Get BMC-end message channel IP address source | In Protocol Specific Record Data<br>- Host IP Assignment Type<br>- Redfish Service IP Discovery Type<br>- Generate the Host-side IP address |
+ | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x03 | Get BMC-end message channel IPv4 address | In Protocol Specific Record Data<br>- Host IP Address Format<br>- Host IP Address |
+ | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x06 | Get BMC-end message channel IPv4 subnet mask | In Protocol Specific Record Data<br>- Host IP Mask<br>- Redfish Service IP Mask |
+ | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x12 | Get BMC-end message channel gateway IP address | None, used to configure edk2 network configuration |
+ | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x14 | Get BMC-end message channel VLAN ID | In Protocol Specific Record Data<br> Redfish Service VLAN ID |
**__NOTE__**
```
--
2.17.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] RedfishPkg: update Readme.md
2023-06-05 14:41 [PATCH] RedfishPkg: update Readme.md Nickle Wang
@ 2023-06-07 1:34 ` Chang, Abner
0 siblings, 0 replies; 2+ messages in thread
From: Chang, Abner @ 2023-06-07 1:34 UTC (permalink / raw)
To: Nickle Wang, devel@edk2.groups.io; +Cc: Igor Kulchytskyy
[AMD Official Use Only - General]
Reviewed-by: Abner Chang <abner.chang@amd.com>
> -----Original Message-----
> From: Nickle Wang <nicklew@nvidia.com>
> Sent: Monday, June 5, 2023 10:41 PM
> To: devel@edk2.groups.io
> Cc: Chang, Abner <Abner.Chang@amd.com>; Igor Kulchytskyy
> <igork@ami.com>
> Subject: [PATCH] RedfishPkg: update Readme.md
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> RedfishClientPkg is moved from edk2-staging repository to
> edk2-redfish-client repository. Update the link in Readme.md
> to new location.
>
> Signed-off-by: Nickle Wang <nicklew@nvidia.com>
> Cc: Abner Chang <abner.chang@amd.com>
> Cc: Igor Kulchytskyy <igork@ami.com>
> ---
> RedfishPkg/Readme.md | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/RedfishPkg/Readme.md b/RedfishPkg/Readme.md
> index 7defe78eb1e0..3156c89f027d 100644
> --- a/RedfishPkg/Readme.md
> +++ b/RedfishPkg/Readme.md
> @@ -5,7 +5,7 @@ UEFI Redfish EDK2 solution is an efficient and secure
> solution for the end-users
>
> Below are the block diagrams of UEFI Redfish EDK2 Implementation.
> ***[EDK2 Redfish Foundation[1]](#[0])*** in the lower part of the figure
> refers to the EDK2 Redfish Foundation, which provides the fundamental EDK2
> drivers to communicate with Redfish service ***([[19]](#[0]) in the above
> figure)***. The Redfish service could be implemented in BMC to manage the
> system, or on the network for managing multiple systems.
>
> -***[EDK2 Redfish Client[2]](#[0])*** in the upper part of the figure refers to
> the EDK2 Redfish client, which is the EDK2 Redfish application used to
> configure platform configurations by consuming the Redfish properties. The
> EDK2 Redfish client can also provision the UEFI platform-owned Redfish
> properties, consume and update Redfish properties as well. The ***[EDK2
> Redfish Feature DXE Drivers [17]](https://github.com/tianocore/edk2-
> staging/blob/edk2-redfish-client/RedfishClientPkg/Readme.md)*** is the
> project under development in EDK2 staging repository. Each EDK2 Redfish
> Feature DXE Driver is designed to communicate with the particular Redfish
> data model defined in the Redfish schema *(e.g. Edk2RedfishBiosDxe driver
> manipulates the properties defined in Redfish BIOS data model)*.
> +***[EDK2 Redfish Client[2]](#[0])*** in the upper part of the figure refers to
> the EDK2 Redfish client, which is the EDK2 Redfish application used to
> configure platform configurations by consuming the Redfish properties. The
> EDK2 Redfish client can also provision the UEFI platform-owned Redfish
> properties, consume and update Redfish properties as well. The ***[EDK2
> Redfish Feature DXE Drivers [17]](https://github.com/tianocore/edk2-
> redfish-client/blob/main/RedfishClientPkg/Readme.md)*** is the project in
> tianocore/edk2-redfish-client repository. Each EDK2 Redfish Feature DXE
> Driver is designed to communicate with the particular Redfish data model
> defined in the Redfish schema *(e.g. Edk2RedfishBiosDxe driver manipulates
> the properties defined in Redfish BIOS data model)*.
>
> ## <a name="[0]">EDK2 Redfish Implementation Diagrams</a>
> 
> @@ -136,16 +136,16 @@ programmatic way to recognize the BMC-exposed
> USB NIC.
> The USB NIC exposed by BMC must be reported as one of the message
> channels as 802.3 LAN/IPMB 1.0 message
> channel.
>
> - | IPMI NetFn | IPMI Command| Purpose | Corresponding Host Interface
> Field|
> - |------------|-------------|---------|-----------------------------------|
> - | App<br>(0x06) | 0x42 | Check the message channel's medium type and
> protocol.<br>Medium: 802.3 LAN<br>Protocol: IPMB 1.0| None|
> - | Transport<br>(0x0C) | 0x02 | Get MAC address of message channel.
> Used to match with the MAC address populated in EFI Device Path of network
> device| None|
> - | Group Ext<br>(0x2C) | Group Extension ID: 0x52<br>Command: 0x02 |
> Check if Redfish bootstrap credential is supported or not.| In Device
> Descriptor Data, Credential Bootstrapping Handle|
> - | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x04 | Get BMC-
> end message channel IP address source| In Protocol Specific Record Data<br>-
> Host IP Assignment Type<br>- Redfish Service IP Discovery Type<br>-
> Generate the Host-side IP address|.
> - | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x03 | Get BMC-
> end message channel IPv4 address| In Protocol Specific Record Data<br>-
> Host IP Address Format<br>- Host IP Address|
> - | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x06 | Get BMC-
> end message channel IPv4 subnet mask| In Protocol Specific Record Data<br>-
> Host IP Mask<br>- Redfish Service IP Mask|
> - | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x12 | Get BMC-
> end message channel gateway IP address| None, used to configure edk2
> network configuration|
> - | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x14 | Get BMC-
> end message channel VLAN ID| In Protocol Specific Record Data<br> Redfish
> Service VLAN ID|
> + | IPMI NetFn | IPMI Command | Purpose
> | Corresponding Host Interface Field
> |
> + | ------------------- | ----------------------------------------- | -----------------------
> ----------------------------------------------------------------------------------------------
> | --------------------------------------------------------------------------------------------
> ----------------------------------------------- |
> + | App<br>(0x06) | 0x42 | Check the message
> channel's medium type and protocol.<br>Medium: 802.3 LAN<br>Protocol:
> IPMB 1.0 | None
> |
> + | Transport<br>(0x0C) | 0x02 | Get MAC address of
> message channel. Used to match with the MAC address populated in EFI
> Device Path of network device | None
> |
> + | Group Ext<br>(0x2C) | Group Extension ID: 0x52<br>Command: 0x02 |
> Check if Redfish bootstrap credential is supported or not.
> | In Device Descriptor Data, Credential Bootstrapping Handle
> |
> + | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x04 | Get
> BMC-end message channel IP address source
> | In Protocol Specific Record Data<br>- Host IP Assignment Type<br>- Redfish
> Service IP Discovery Type<br>- Generate the Host-side IP address |
> + | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x03 | Get
> BMC-end message channel IPv4 address
> | In Protocol Specific Record Data<br>- Host IP Address Format<br>- Host IP
> Address |
> + | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x06 | Get
> BMC-end message channel IPv4 subnet mask
> | In Protocol Specific Record Data<br>- Host IP Mask<br>- Redfish Service IP
> Mask |
> + | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x12 | Get
> BMC-end message channel gateway IP address
> | None, used to configure edk2 network configuration
> |
> + | Transport<br>(0x0C) | Command: 0x02<br>Parameter: 0x14 | Get
> BMC-end message channel VLAN ID
> | In Protocol Specific Record Data<br> Redfish Service VLAN ID
> |
>
> **__NOTE__**
> ```
> --
> 2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-06-07 1:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-05 14:41 [PATCH] RedfishPkg: update Readme.md Nickle Wang
2023-06-07 1:34 ` Chang, Abner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox