Wenyi, If you look under the Build results <Platform>/<DEBUG/RELEASE>_<COMPILER>/AArch64/Edk2/ArmPkg/Drivers/ArmGic/ (hopefully I got that right) and go down a little bit you will see the build

Thanks Laszlo to explain that. One minor comments: TCG adopted Secure MOR in latest MOR 1.1 spec in 2019 -

Ah, thanks. :) I'll have to refresh my local PDF then! Laszlo

Hi Sandeep, You should probably discuss on this list what you want to add to the main tree before sending patches, you might get good pointers. Otherwise, there is a good guide as to how it works

Thanks, Andrew, Laszlo and liming, with your help I find the module which really own the warning. As the compile is multithreading, the order in compile log is not right. The module which cause

I checked my platform DSC and there's UefiDriverEntryPoint|MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf in the section [LibraryClasses.common]. I'm not sure why _ModuleEntryPoint can't

+Jiewen, comments below Side comment: Wow! I very much suspected that the memory overwrite is performed on physical platforms via proprietary DIMM or board access, not via plain RAM writes. The

Which emulator? Ovmf? Which USB? Real or Virtual? Thanks, Guomin

Hi, We have a number of MinnowBoards (both Turbot and Max variants) here that are used for various Linux development purposes, including having a number that are used in our LAVA farm which among

Hi Leif, Just want to make sure you received my previous mail, do you have any comments for the edk2-platform formal release? Waiting for you reply. Thanks! -----邮件原件----- 发件人:

Hi, I am wondering is there a way to expose an USB device to the emulator and develop the usb driver over the emulator?

ModuleEntryPoint is provided by EntryPointLib. This driver links MdePkg\Library\UefiDriverEntryPoint. Please check.

Jeff: You mean the memory range specified by PHIT resource hob is selected by CoreInitializeMemoryServices(). This memory range includes PEI memory and the allocated memory. So, there is no free

The UefiDriverEntryPoint lib class in the [Sources] section in "ArmPkg/Drivers/ArmGic/ArmGicDxe.inf" should be resolved by your platform DSC

I think I've always just ignored these... Laszlo

Hi all, I meet some compile warning in BaseTools，the version of EDK2 is edk2-stable201903, as I am not familiar with Antlr grammer, I don't know how to fix it. Could someone give me a hand,

Hi, all I use edk2-stable201903 in my project and meet a compile warning like

#2 is the case we are in, we have data that is loaded by our pre-UEFI bootloaders into memory that should behave as boot services memory (OS can reclaim this) When we setup our HOB list we added a

Do you mean (1) a physically reserved memory address range (EFI_RESOURCE_MEMORY_RESERVED), or (2) normal RAM (EFI_RESOURCE_SYSTEM_MEMORY) that is meant to be "repurposed" (= pre-allocated) in PEI as

It looks like CoreInitializeMemoryServices (https://github.com/tianocore/edk2/blob/dd5c7e3c5282b084daa5bbf0ec229cec699b2c17/MdeModulePkg/Core/Dxe/Gcd/Gcd.c#L2116) does not honor any memory allocations