From: "Chao Li" <lichao@loongson.cn>
To: devel@edk2.groups.io
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Zhiguang Liu <zhiguang.liu@intel.com>
Subject: [staging/LoongArch PATCH v1 06/33] MdePkg/Include: Add LOONGARCH related definitions EDK2 CI.
Date: Wed, 9 Feb 2022 14:27:10 +0800 [thread overview]
Message-ID: <20220209062737.2961153-7-lichao@loongson.cn> (raw)
In-Reply-To: <20220209062737.2961153-1-lichao@loongson.cn>
HTTP/PXE boot LOONGARCH64 related definitions for EDK2 CI.
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Zhiguang Liu <zhiguang.liu@intel.com>
Signed-off-by: Chao Li <lichao@loongson.cn>
---
MdePkg/Include/IndustryStandard/Dhcp.h | 41 +++++++++++++++-----------
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git a/MdePkg/Include/IndustryStandard/Dhcp.h b/MdePkg/Include/IndustryStandard/Dhcp.h
index f209f1b2eb..086d24422d 100644
--- a/MdePkg/Include/IndustryStandard/Dhcp.h
+++ b/MdePkg/Include/IndustryStandard/Dhcp.h
@@ -4,6 +4,7 @@
Copyright (c) 2016, Intel Corporation. All rights reserved.<BR>
Copyright (c) 2020, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
+ Copyright (c) 2022, Loongson Technology Corporation Limited. All rights reserved.<BR>
SPDX-License-Identifier: BSD-2-Clause-Patent
**/
@@ -259,24 +260,28 @@ typedef enum {
/// These identifiers are defined by IETF:
/// http://www.ietf.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml
///
-#define PXE_CLIENT_ARCH_X86_BIOS 0x0000 /// x86 BIOS for PXE
-#define PXE_CLIENT_ARCH_IPF 0x0002 /// Itanium for PXE
-#define PXE_CLIENT_ARCH_IA32 0x0006 /// x86 uefi for PXE
-#define PXE_CLIENT_ARCH_X64 0x0007 /// x64 uefi for PXE
-#define PXE_CLIENT_ARCH_EBC 0x0009 /// EBC for PXE
-#define PXE_CLIENT_ARCH_ARM 0x000A /// Arm uefi 32 for PXE
-#define PXE_CLIENT_ARCH_AARCH64 0x000B /// Arm uefi 64 for PXE
-#define PXE_CLIENT_ARCH_RISCV32 0x0019 /// RISC-V uefi 32 for PXE
-#define PXE_CLIENT_ARCH_RISCV64 0x001B /// RISC-V uefi 64 for PXE
-#define PXE_CLIENT_ARCH_RISCV128 0x001D /// RISC-V uefi 128 for PXE
+#define PXE_CLIENT_ARCH_X86_BIOS 0x0000 /// x86 BIOS for PXE
+#define PXE_CLIENT_ARCH_IPF 0x0002 /// Itanium for PXE
+#define PXE_CLIENT_ARCH_IA32 0x0006 /// x86 uefi for PXE
+#define PXE_CLIENT_ARCH_X64 0x0007 /// x64 uefi for PXE
+#define PXE_CLIENT_ARCH_EBC 0x0009 /// EBC for PXE
+#define PXE_CLIENT_ARCH_ARM 0x000A /// Arm uefi 32 for PXE
+#define PXE_CLIENT_ARCH_AARCH64 0x000B /// Arm uefi 64 for PXE
+#define PXE_CLIENT_ARCH_RISCV32 0x0019 /// RISC-V uefi 32 for PXE
+#define PXE_CLIENT_ARCH_RISCV64 0x001B /// RISC-V uefi 64 for PXE
+#define PXE_CLIENT_ARCH_RISCV128 0x001D /// RISC-V uefi 128 for PXE
+#define PXE_CLIENT_ARCH_LOONGARCH32 0x0025 /// LOONGARCH uefi 32 for PXE
+#define PXE_CLIENT_ARCH_LOONGARCH64 0x0027 /// LOONGARCH uefi 64 for PXE
-#define HTTP_CLIENT_ARCH_IA32 0x000F /// x86 uefi boot from http
-#define HTTP_CLIENT_ARCH_X64 0x0010 /// x64 uefi boot from http
-#define HTTP_CLIENT_ARCH_EBC 0x0011 /// EBC boot from http
-#define HTTP_CLIENT_ARCH_ARM 0x0012 /// Arm uefi 32 boot from http
-#define HTTP_CLIENT_ARCH_AARCH64 0x0013 /// Arm uefi 64 boot from http
-#define HTTP_CLIENT_ARCH_RISCV32 0x001A /// RISC-V uefi 32 boot from http
-#define HTTP_CLIENT_ARCH_RISCV64 0x001C /// RISC-V uefi 64 boot from http
-#define HTTP_CLIENT_ARCH_RISCV128 0x001E /// RISC-V uefi 128 boot from http
+#define HTTP_CLIENT_ARCH_IA32 0x000F /// x86 uefi boot from http
+#define HTTP_CLIENT_ARCH_X64 0x0010 /// x64 uefi boot from http
+#define HTTP_CLIENT_ARCH_EBC 0x0011 /// EBC boot from http
+#define HTTP_CLIENT_ARCH_ARM 0x0012 /// Arm uefi 32 boot from http
+#define HTTP_CLIENT_ARCH_AARCH64 0x0013 /// Arm uefi 64 boot from http
+#define HTTP_CLIENT_ARCH_RISCV32 0x001A /// RISC-V uefi 32 boot from http
+#define HTTP_CLIENT_ARCH_RISCV64 0x001C /// RISC-V uefi 64 boot from http
+#define HTTP_CLIENT_ARCH_RISCV128 0x001E /// RISC-V uefi 128 boot from http
+#define HTTP_CLIENT_ARCH_LOONGARCH32 0x0026 /// LOONGARCH uefi 32 boot from http
+#define HTTP_CLIENT_ARCH_LOONGARCH64 0x0028 /// LOONGARCH uefi 64 boot from http
#endif
--
2.27.0
next prev parent reply other threads:[~2022-02-09 6:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 6:27 [staging/LoongArch PATCH v1 00/33] Add a new architecture Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 01/33] FatPkg: Add LOONGARCH64 architecture for EDK2 CI Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 02/33] FmpDevicePkg: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 03/33] NetworkPkg: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 04/33] NetworkPkg/HttpBootDxe: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 05/33] CryptoPkg: " Chao Li
2022-02-09 6:27 ` Chao Li [this message]
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 07/33] SecurityPkg: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 08/33] ShellPkg: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 09/33] UnitTestFrameworkPkg: " Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 10/33] MdePkg/DxeServicesLib: Add LOONGARCH64 architecture Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 11/33] MdeModulePkg: Use LockBoxNullLib for LOONGARCH64 Chao Li
2022-02-09 6:27 ` [staging/LoongArch PATCH v1 12/33] .python/SpellCheck: Add "Loongson" and "LOONGARCH" to "words" section Chao Li
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=20220209062737.2961153-7-lichao@loongson.cn \
--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