Brian, I think all the PEI Allocate Pool does is make a HOB [1]. I don’t think we can remove HOBs when memory is freed as that would change pointers to pool. It may be possible to mark a region as fre

I’m guessing all the CI testing is on Python 3.8.x I noticed one of the CI pipes is asking for Python 3.8 [1] [1] https://github.com/tianocore/edk2/blob/master/.azurepipelines/Ubuntu-PatchCheck.yml Th

I though the issue was on x86_64 since by default that does not support relocations in .text sections. The maintainer mentioned this should work for x86_64 but is not really tested. If it works in our

I reached out to the Xcode ld64 maintainer to make sure it is safe to use -read_only_relocs suppress this way. Thanks, Andrew Fish

That looks like an issue with using Python 3.9 as it changed tostring to tobyte.

Marvin, I’ll look into this. The history here is the original ld64 flags are what was required for proper function. I got them directly from the main ld64 maintainer. Big picture ld64 is the macOS and

That library dependency should be resolved by including MdePkg/MdeLibs.dsc.inc in the dSC file? /Volumes/Case/edk2(master)>git grep "MdePkg/MdeLibs.dsc.inc" ArmPkg/ArmPkg.dsc:36:!include MdePkg/MdeLib

Mike, FYI you are not subscribed to the mailing list so all your posts require a humans approval, so that is the delay in them showing up.. I hit something like this in another context. I root caused

For the C builds the tools_def.txt file uses $(IMAGE_ENTRY_POINT). The build maps that over to the _ModelEntryPoint label I mentioned. It would probably be good to sue the same symbol. The C we have i

The general answer for edk2 is and library that a `CONSTRUCTOR =` statement in its INF that lib constructor will get called when the Driver/App is started. The actually entry point for a Driver/App is

This is basically: (*PeiServices)->InstallPeiMemory (PeiServices, MemoryBegin, MemoryLength); This is how you tell the PEI Core the location of the memory that will can be used in PEI. It basically ge

Mike, This sounds like a conversation we had years ago? I think we concluded we needed to write stuff in assembler and not depend on implementation choices of the compiler with regard to registers usa

I’m a little confused on why we can’t put an ARM FV at address 0x00000000 [1]? Obviously the zero vector for the FV is getting patch as this ARM code is jumping to the 1st byte of the FV when it is pr

In edk2 speak Base just means does not depend on any phase of boot, so basically standalone code. So you can pull a Base lib into SEC, PEI, DXE, SMM, etc. We never interned different Class Names for l

It looks like BaseSortLib and and SortLib are the same library class so you should only have one. /Volumes/Case/edk2(master)>git grep --recurse-submodules SortLib -- \*.inf | grep LIBRARY_CLASS MdeMod

I think we need to -D OPENSSL_NO_APPLE_CRYPTO_RANDOM in the INF. Thanks, Andrew Fish

What is pulling in Availability.h? That sound more like and #ifdef issue in some 3rd party header? I think I might have seen that in SSL headers?

I realize I can use syntax like this to control the construction of an option ROM from an FDF file. 1 [OptionRom.AtapiPassThru] 2 INF USE = IA32 OptionRomPkg/AtapiPassThruDxe/AtapiPassThruDxe.inf { 3

Sebastien, The PCD’s end up being build configurable. They can get compiled into constants, call a database. The database entries can get set by code, or mapped to NVRAM variables etc. Some of the PCD

Sebastien, The UEFI ROMs generally contain sets of PE/COFF images (drivers, apps, etc) that execute not at their linked address. These PE/COFF images have been stripped of debug information and option