If they happen a lot maybe they should be DEBUG_VERBOSE? Thanks, Andrew Fish

Are those DEBUG prints or report status code? Thanks, Andrew Fish

Rebecca, gBS->Stall() is built on top [1] of the Metronome Architectural Protocol [2]. You should look at how the platform implements the Metronome Architectural Protocol. It looks like most platform

Vincent, Thanks! I’d forgotten about that path. The other answer is defer the work to a DXE driver that runs 64-bit x86. Thanks, Andrew Fish

The BDS is what runs after all the discovered drivers have been dispatched. The BDS processes all those UEFI NVRAM variables I references, and sets platform defaults. That seems very Rube Goldberg. Th

The UEFI Shell drivers command is managing UEFI Driver Model Drivers [1]. A UEFI Driver Model Driver has no depex and publishes an EFI Driver Binding protocol [2]. The idea is the BDS (platform) can n

I assume you are talking about x86? This is more complex than just instruction prefix. You need the CPU to be setup in big real mode via the GDT, so you basically have a 32-bit environment setup via G

Do you need to run it from FLASH? Or do you just want to run it? What I usually do with QEMU is pass -hda fat:rw:Build/OvmfX64/DEBUG_XCODE5/X64 to mount a directory on my system in QEMU. This should s

If you are building with the firmware use the DebugLib in the INF and DEBUG(); macros. DEBUG((DEBUG_ERROR, “It works ”)); Also by setting your Depex to TRUE you are basically asking to run before the

I understand, but I think there are other cases when you can query for more specific information. For example you can get info on how to write an EFI PCI Root Bridge drive, and the ACPI methods also i

Is it possible to query the address from fw_cfg? Thanks, Andrew Fish

Reviewed-by: Andrew Fish <afish@...>

That is a missing EFIAPI.

Rebecca, I think this feature flag is going to control the output of edk2 DEBUG. In an abstract sense DEBUG is not Terminal or ConOut. It could be mapped to the same device, but it does not have to be

Rafael, I’m not sure this matches exactly what you are looking for, but the OVMF (Virtual Machine) has some configuration options around HTTPS boot [1]. That might be a good place to start. [1] https:

Maybe having the check last would be cleaner. diff --git a/BaseTools/Source/C/DevicePath/GNUmakefile b/BaseTools/Source/C/DevicePath/GNUmakefile index c217674345b1..17f213879e82 100644 --- a/BaseTools

Rebecca, FYI /usr/bin/gcc has been a redirector into clang for a lot of years. The build picks different default sets of complier flags based on build type. There is already code that assumes gcc == c

Rohit, FYI I seem to remember when we added the bitfield verbiage to the UEFI Spec it was because there was lots of platform code that was using it. We did not really want to encourage its use it in p

Probably better NOT to use bitfields in APIs that are produced and consumed by different worlds. While the the UEFI does speak to the bit order of or a bitfield the rules around packing of bitfields i

Did you figure this out? The per compiler flags come from BaseTools/Conf/tools_def.template. When you do the edksetup.sh it gets copied to Conf/tools_def.ttxt and that is what the build uses. The rule