[edk2] [PATCH v4 0/5] MdeModulePkg: add support for non-discoverable devices

The rationale for this series is the fact that many ARM platforms implement some form of PCI 'emulation', to allow non-discoverable devices that implement standardized host controller interfaces (i.e., EHCI, AHCI) to be controlled by the generic EDK2 drivers, which are layered on top of the PCI

[edk2] [PATCH v4 2/5] MdeModulePkg: introduce helper library to register non-discoverable devices

Non-discoverable devices need to be registered explicitly by the platform. Introduce a helper library that takes care of this. This implementation currently only supports registering devices that are covered by one or more MMIO resources. The underlying protocol allows for more flexibility than

[edk2] [PATCH v4 3/5] MdeModulePkg: implement generic PCI I/O driver for non-discoverable devices

This implements support for non-discoverable PCI compatible devices, i.e, devices that are not on a PCI bus but that can be controlled by generic PCI drivers in EDK2. This is implemented as a UEFI driver, which means we take full advantage of the UEFI driver model, and only instantiate those

[edk2] [PATCH v4 1/5] MdeModulePkg: introduce non-discoverable device protocol

Introduce a protocol that can be exposed by a platform for devices that are not discoverable, usually because they are wired straight to the memory bus rather than to an enumerable bus like PCI or USB. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel

[edk2] [PATCH v4 4/5] MdeModulePkg/NonDiscoverablePciDeviceDxe: add support for non-coherent DMA

Add support for non-coherent DMA, either by performing explicit cache maintenance when DMA mappings are aligned to the CPU's DMA buffer alignment, or by bounce buffering via uncached mappings otherwise. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel

[edk2] [PATCH v4 5/5] Omap35xxPkg/PciEmulation: port to new non-discoverable device infrastructure

Move to the new non-discoverable device protocols for wiring the PCI based EHCI controller driver to the non-discoverable EHCI controller found on the OMAP 3530. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel ---

Re: [edk2] [PATCH v3 1/1] MdeModulePkg/EbcDxe: add EBC Debugger configuration application

Reviewed-by: jiewen@intel.com > -Original Message- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Pete Batard > Sent: Friday, November 25, 2016 1:00 AM > To: edk2-devel@lists.01.org > Cc: Yao, Jiewen > Subject: [edk2] [PATCH v3 1/1]

Re: [edk2] [PATCH v3 1/5] MdeModulePkg: introduce non-discoverable device protocol

On 18 November 2016 at 13:50, Ard Biesheuvel wrote: > > On 18 Nov 2016, at 14:39, Ni, Ruiyu wrote: > >> 1. Can you add "PCI" keyword into the protocol name? >> e.g.: EDKII_NON_DISCOVERABLE_PCI_DEVICE_PROTOCOL_GUID >>

Re: [edk2] [Patch] MdeModulePkg/NetLib: Handle an invalid IPv6 address case

Reviewed-by: Zhang Lubo -Original Message- From: Wu, Jiaxin Sent: Friday, November 25, 2016 2:16 PM To: edk2-devel@lists.01.org Cc: Zhang, Lubo ; Fu, Siyuan ; Ye, Ting Subject: [Patch]

[edk2] [PATCH] IntelFsp2Pkg: Add PACKAGES_PATH support

Add PACKAGES_PATH support in GenCfgOpt.py Cc: Maurice Ma Cc: Jiewen Yao Cc: Giri P Mudusuru Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Richard Thomaiyar ---

[edk2] [patch] NetworkPkg:Add scriptable configuration to iSCSI driver by leveraging x-UEFI.

Enable iSCSI keywords configuration based on x-UEFI name space. we introduce new PCD to control the attempt numbers which will be created in non activated state, besides the Attempt name is changed to READ_ONLY attribute in UI. We can invoke KEYWORD HANDLER Protocol to configure the related

Re: [edk2] [PATCH v2 5/5] UefiCpuPkg/DxeMpLib: Remove unnecessary ret instruction

On 11/25/16 07:03, Jeff Fan wrote: > Reported-by: Laszlo Ersek > Cc: Laszlo Ersek > Cc: Feng Tian > Cc: Michael D Kinney > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Jeff Fan

Re: [edk2] [PATCH v2 4/5] UefiCpuPkg/DxeMpLib: Fix bug when getting target C-State from eax

On 11/25/16 07:03, Jeff Fan wrote: > AP will get target C-State from eax[7:4]. We do shift in ebx firstly before > set > to eax. It will lead ebx is correct in the next time. Please replace the word "correct" with "incorrect" in the commit message -- without the patch, ebx is wrong at the second

Re: [edk2] [PATCH v2 2/5] UefiCpuPkg/DxeMpLib: Allocate new safe stack < 4GB

On 11/25/16 07:03, Jeff Fan wrote: > For long mode DXE, we will disable paging on AP to protected mode to execute > AP > safe loop code in reserved memory range under 4GB. But we forget to allocate > stack for AP under 4GB and AP still are using original AP stack. If original > AP > stack is

Re: [edk2] [PATCH v2 3/5] UefiCpuPkg/DxeMpLib: Make sure APs in safe loop code

On 11/25/16 07:03, Jeff Fan wrote: > Add one semaphore to make sure BSP to wait till all APs run in AP safe loop > code. > > Cc: Laszlo Ersek > Cc: Feng Tian > Cc: Michael D Kinney > Contributed-under: TianoCore Contribution

Re: [edk2] [PATCH 0/3] Remove the ArmPkg LinuxLoader

On 22 November 2016 at 17:09, Ryan Harkin wrote: > On 21 November 2016 at 17:28, Ryan Harkin wrote: >> On 21 November 2016 at 12:29, Ard Biesheuvel >> wrote: >>> On 21 November 2016 at 12:28, Ard Biesheuvel

Re: [edk2] [PATCH v2 1/5] UefiCpuPkg/DxeMpLib: Get safe AP loop handler from global variable

On 11/25/16 07:03, Jeff Fan wrote: > AP loop function is already saved into global variable, needn't to get it from > AP function parameter. > > Cc: Laszlo Ersek > Cc: Feng Tian > Cc: Michael D Kinney > Contributed-under:

Re: [edk2] [PATCH v2 0/5] UefiCpuPkg/DxeMpLib: Allocate new safe stack < 4GB

On 11/25/16 07:03, Jeff Fan wrote: > Allocate safe AP stack under 4GB and make sure BSP wait till all APs running > in > safe code. > > v2: > 1. Update #1 to address the comments in >https://lists.01.org/pipermail/edk2-devel/2016-November/005136.html > 2. Update #2 to address the

Re: [edk2] [PATCH 0/2] Virtual Memory Map Fix for VE

On 24 November 2016 at 19:56, wrote: > From: Evan Lloyd > > This patch set fixes an allocation error in the Versatile Express > RTSMMem.c. > An extra patch is included that merely tidies the code format before the > real fix is applied. > > The resultant