Reviewed-by: Ray Ni <ray.ni@...>

+} UEFI_PAYLOAD_DEBUG_PRINT_ERROR_LEVEL; + +#pragma pack() + +#define UNIVERSAL_PAYLOAD_DEBUG_PRINT_ERROR_LEVEL_REVISION 1 Please change above macro to

Christine: Can you try the option -Wno-unknown-warning to see whether it disables the warning about an unrecognized command line option? Thanks Liming we "-Wno-error=stringop-overflow"

Hello, I’m Théo, a French 1st year master’s student, specialized in embedded systems engineering. I’m interested in joining EDK II development as part of the Google Summer of Code

Thanks Min Series: Reviewed-by: Jiewen Yao <Jiewen.yao@...>

Since the gcc12 has the incompatible change from GCC5.4, I'd also suggest we could create a new TOOL CHAIN for gcc12. The error reports I collected show in gcc5.4 , "-Wno-error=stringop-overflow" is

Acked-by: Liming Gao <gaoliming@...> the from in valuable is following series. planned at for and Samples the functionality 100644

The change in MdePkg is good to me. Reviewed-by: Liming Gao <gaoliming@...>

Hi Hoffmann, I received some reports that some platforms are using gcc5.4. With this patch, these platform builds are still broken. Would you like to revert the original commits? Thanks, Christine

Change the DebugPrintErrorLevelLib instance in UefiPayloadPkg.dsc to allow bootloader to config DebugPrintErrorLevel. Cc: Ray Ni <ray.ni@...> Cc: Maurice Ma <maurice.ma@...> Cc: Benjamin

It consumes the HOB defined in UefiPayloadPkg/Include/Guid/DebugPrintErrorLevel.h, and allow bootloader to config DebugPrintErrorLevel. Cc: Ray Ni <ray.ni@...> Cc: Maurice Ma

This patch has both UNIVERSAL_PAYLOAD_DEBUG_PRINT_ERROR_LEVEL and UEFI_PAYLOAD_DEBUG_PRINT_ERROR_LEVEL. Please double check this patch if it could pass build. Thanks, Guo

Reviewed-by: Guo Dong <guo.dong@...>

When I do a measured boot of OVMF, I get a load of records including the two EV_EFI_PLATFORM_FIRMWARE_BLOB events, which, according to the code in Tcg2Pei.c are supposed to be measuring PEIFV and

Hey Tejesh, Sorry your mail doesn't get much activity. I think parsing-related things are most important: - String functions in BaseLib:

How does the PEI phase know that this page in the middle is still unvalidated? I see this code: STATIC SNP_PRE_VALIDATED_RANGE mPreValidatedRange[] = { // The below address

Yes, that should be alright as long as the SNP_SEC_MEM_BASE_DESC_3 start from PcdOvmfSecPeiTempRamBase. In PEI phase, we validate all the unvalidated range. So, as long as SEC phase is not using

Gerd actually wants to change SNP_SEC_MEM_BASE_DESC_3 to start from PcdOvmfSecPeiTempRamBase, which is 0x010000. Supposedly no one uses the single page at 0x00F000 . -Dov

Lets look at the OvmfPkgX64.fdf is ... 0x00E000|0x001000

Reviewed-by Sean Rhodes <sean@...>