From: "Tuan Phan" <tphan@ventanamicro.com>
To: devel@edk2.groups.io
Cc: andrei.warkentin@intel.com, sunilvl@ventanamicro.com,
Tuan Phan <tphan@ventanamicro.com>
Subject: [PATCH] OvmfPkg: RiscVVirt: Fix network drivers not be built
Date: Tue, 6 Jun 2023 16:04:15 -0700 [thread overview]
Message-ID: <20230606230415.9905-1-tphan@ventanamicro.com> (raw)
Only need to include Network.dsc.inc to have all network
drivers/components be built. Otherwise, there were missing definition
that prevent them from be built for RiscVVirt platform.
Signed-off-by: Tuan Phan <tphan@ventanamicro.com>
---
OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc b/OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc
index 414d186179fb..5281b611d453 100644
--- a/OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc
+++ b/OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc
@@ -52,6 +52,7 @@
!include MdePkg/MdeLibs.dsc.inc
+!include NetworkPkg/Network.dsc.inc
[BuildOptions]
GCC:RELEASE_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
@@ -69,8 +70,6 @@
#
################################################################################
-!include NetworkPkg/NetworkDefines.dsc.inc
-
!include OvmfPkg/RiscVVirt/RiscVVirt.dsc.inc
!include MdePkg/MdeLibs.dsc.inc
@@ -124,8 +123,6 @@
UefiScsiLib|MdePkg/Library/UefiScsiLib/UefiScsiLib.inf
PciExpressLib|OvmfPkg/Library/BaseCachingPciExpressLib/BaseCachingPciExpressLib.inf
-#!include NetworkPkg/NetworkBuildOptions.dsc.inc
-
################################################################################
#
# Pcd Section - list of all EDK II PCD Entries defined by this Platform.
@@ -164,11 +161,6 @@
gEfiMdeModulePkgTokenSpaceGuid.PcdSerialClockRate|3686400
gEfiMdeModulePkgTokenSpaceGuid.PcdSerialRegisterStride|1
- #
- # Network Pcds
- #
-!include NetworkPkg/NetworkPcds.dsc.inc
-
gEfiMdeModulePkgTokenSpaceGuid.PcdResetOnMemoryTypeInformationChange|FALSE
gEfiMdeModulePkgTokenSpaceGuid.PcdBootManagerMenuFile|{ 0x21, 0xaa, 0x2c, 0x46, 0x14, 0x76, 0x03, 0x45, 0x83, 0x6e, 0x8a, 0xb6, 0xf4, 0x66, 0x23, 0x31 }
@@ -397,11 +389,6 @@
NULL|OvmfPkg/Library/BlobVerifierLibNull/BlobVerifierLibNull.inf
}
- #
- # Networking stack
- #
-!include NetworkPkg/NetworkComponents.dsc.inc
-
NetworkPkg/UefiPxeBcDxe/UefiPxeBcDxe.inf {
<LibraryClasses>
NULL|OvmfPkg/Library/PxeBcPcdProducerLib/PxeBcPcdProducerLib.inf
--
2.25.1
reply other threads:[~2023-06-07 0:29 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=20230606230415.9905-1-tphan@ventanamicro.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