From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH v4 0/6] Fix PciBus to accept Spec values as BarIndex and Alignment
Date: Wed, 8 Feb 2017 17:42:57 +0800 [thread overview]
Message-ID: <20170208094258.59568-1-ruiyu.ni@intel.com> (raw)
If a platform developer follows the PI spec to write an
IncompatiblePciDeviceSupport driver, due to a spec complaince
bug in PciBus driver, the IncompatiblePciDeviceSupport driver
may not work as expected. The patches fix PciBus to follow Spec
to accept Spec defined values.
v2: Use DISABLE_NEW_DEPRECATED_INTERFACES to deprecate macros.
v3: Use MAX_UINT64/MAX_UINTN to replace (UINT64)-1 and (UINTN)-1.
v4: Deprecate PCI_ACPI_UNUSED and PCI_BAR_NOCHANGE.
Ruiyu Ni (6):
MdeModulePkg/PciSioSerialDxe: Use MAX_UINT8 instead of PCI_BAR_ALL
MdeModulePkg/PciBus: Accept Spec values as BarIndex and Alignment
MdeModulePkg/IncompatiblePciDevice: Do not use deprecated macros
MdeModulePkg/IncompatiblePci: Use MAX_UINTN to match any IDs
OvmfPkg/IncompatiblePci: Do not use deprecated macros
MdePkg/Pci22.h: Deprecate out-of-Spec IncompatiblePciDevice macros
.../IncompatiblePciDeviceSupport.c | 108 ++++++++++-----------
.../Bus/Pci/PciBusDxe/PciEnumeratorSupport.c | 36 ++++---
MdeModulePkg/Bus/Pci/PciSioSerialDxe/Serial.c | 2 +-
MdePkg/Include/IndustryStandard/Pci22.h | 24 +++--
.../IncompatiblePciDeviceSupport.c | 13 +--
5 files changed, 100 insertions(+), 83 deletions(-)
--
2.9.0.windows.1
next reply other threads:[~2017-02-08 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 9:42 Ruiyu Ni [this message]
2017-02-08 9:42 ` [PATCH v4 6/6] MdePkg/Pci22.h: Deprecate out-of-Spec IncompatiblePciDevice macros Ruiyu Ni
2017-02-08 10:44 ` Laszlo Ersek
2017-02-09 2:10 ` Ni, Ruiyu
2017-02-09 2:06 ` Ruiyu Ni
2017-02-09 19:47 ` Laszlo Ersek
2017-02-10 3:13 ` Gao, Liming
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=20170208094258.59568-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