From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0E2E581F9C for ; Wed, 25 Jan 2017 22:09:31 -0800 (PST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP; 25 Jan 2017 22:09:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,287,1477983600"; d="scan'208";a="57682403" Received: from ray-dev.ccr.corp.intel.com ([10.239.9.25]) by fmsmga005.fm.intel.com with ESMTP; 25 Jan 2017 22:09:30 -0800 From: Ruiyu Ni To: edk2-devel@lists.01.org Date: Thu, 26 Jan 2017 14:09:22 +0800 Message-Id: <20170126060927.352436-1-ruiyu.ni@intel.com> X-Mailer: git-send-email 2.9.0.windows.1 Subject: [PATCH 0/5] Fix PciBus to accept Spec values as BarIndex and Alignment X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 06:09:31 -0000 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. Ruiyu Ni (5): MdePkg/Pci22.h: Deprecate out-of-Spec IncompatiblePciDevice macros 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 -1 to match any IDs .../IncompatiblePciDeviceSupport.c | 97 +++++++++++----------- .../Bus/Pci/PciBusDxe/PciEnumeratorSupport.c | 17 ++-- MdeModulePkg/Bus/Pci/PciSioSerialDxe/Serial.c | 2 +- MdePkg/Include/IndustryStandard/Pci22.h | 16 ++-- 4 files changed, 67 insertions(+), 65 deletions(-) -- 2.9.0.windows.1