From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH] MdeModulePkg/MdeModulePkg.dec: Fix EBC build failure of PciBus driver
Date: Tue, 11 Oct 2016 13:01:13 +0800 [thread overview]
Message-ID: <20161011050113.197540-1-ruiyu.ni@intel.com> (raw)
When PciBus is built as EBC, PcdPciDegradeResourceForOptionRom does
not have associated value resulting build failure.
The patch sets the default value to TRUE, covering the EBC ARCH.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
---
MdeModulePkg/MdeModulePkg.dec | 1 -
1 file changed, 1 deletion(-)
diff --git a/MdeModulePkg/MdeModulePkg.dec b/MdeModulePkg/MdeModulePkg.dec
index f870b83..42fef75 100644
--- a/MdeModulePkg/MdeModulePkg.dec
+++ b/MdeModulePkg/MdeModulePkg.dec
@@ -746,7 +746,6 @@ [PcdsFeatureFlag]
# @Prompt Turn on PS2 Mouse Extended Verification
gEfiMdeModulePkgTokenSpaceGuid.PcdPs2MouseExtendedVerification|TRUE|BOOLEAN|0x00010075
-[PcdsFeatureFlag.X64]
## Indicates whether 64-bit PCI MMIO BARs should degrade to 32-bit in the presence of an option ROM
# On X64 platforms, Option ROMs may contain code that executes in the context of a legacy BIOS (CSM),
# which requires that all PCI MMIO BARs are located below 4 GB
--
2.9.0.windows.1
next reply other threads:[~2016-10-11 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 5:01 Ruiyu Ni [this message]
2016-10-11 10:52 ` [PATCH] MdeModulePkg/MdeModulePkg.dec: Fix EBC build failure of PciBus driver Laszlo Ersek
2016-10-11 17:03 ` Ard Biesheuvel
2016-10-12 2:36 ` Ni, Ruiyu
2016-10-12 7:08 ` Laszlo Ersek
2016-10-12 8:36 ` Ard Biesheuvel
2016-10-12 8:51 ` Tian, Feng
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=20161011050113.197540-1-ruiyu.ni@intel.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