For this patch series: Reviewed-by: Thomas Abraham <thomas.abraham@...> [...] IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you

Pushed as 8cdd4cb7c71e..f7c08b9bae56 Thanks. Regards, Sami Mujawar

A bit more work is needed for that (but I agree it should be done), because we have this additionally: QemuFwCfgSelectItem (QemuFwCfgItemInitrdSize); InitrdSize = (UINTN)QemuFwCfgRead32 (); if

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

Liming, I happen to notice the below patches which you sent out two years ago: https://edk2.groups.io/g/devel/topic/31354044#41053 It seems to me that I can drop my CLANGDWARF change completely and

Pushed as 86984c17d562..8cdd4cb7c71e, with minor changes to patch 4 and 7. Thanks. Regards, Sami Mujawar

Hi Rebecca, Thank you for this patch. Reviewed-by: Sami Mujawar <sami.mujawar@...> Regards, Sami Mujawar

This patch adds platform specific DSDT generator and Clk dsdt properties for LS1046AFRWY platform. Signed-off-by: Vikas Singh <vikas.singh@...> --- .../AcpiTablesInclude/Dsdt/Clk.asl

This patch set extends Configuration Manager (CM) and its services to leverage the Dynamic ACPI support for NXP's LS1046aFrwy

This change set intend to add a generic method to get access to SoC's Silicon Version Register (SVR) and its handling for LS1046aFrwy platform. Signed-off-by: Vikas Singh

Summary - 1.Configuration Manager(CM) is a common implementation and should not evaluate the SoC version using macro's However CM must directly consume SoC ver string from platfrom who is

Hi Rebecca, Thank you for this patch. Reviewed-by: Sami Mujawar <sami.mujawar@...> Regards, Sami Mujawar

This patch series basically aims to extend the Dynamic ACPI framework towards NXP's LS1046AFRWY platform. Refer- https://edk2.groups.io/g/devel/message/71709 The change set in the series is in below

... I don't have any problems with that - I take it this means we can drop the QemuFwCfgLib dependency from GenericQemuLoadImageLib altogether, right? This sounds like a good approach to me.

This commit add option which allows reset content of Secure Boot keys and databases to default variables. Signed-off-by: Grzegorz Bernacki <gjb@...> ---

This commits adds modules related to initialization and usage of default Secure Boot key variables to SecurityPkg. Signed-off-by: Grzegorz Bernacki <gjb@...> --- SecurityPkg/SecurityPkg.dec

This application allows user to force key enrollment from Secure Boot default variables. Signed-off-by: Grzegorz Bernacki <gjb@...> ---

This driver initializes default Secure Boot keys and databases based on keys embedded in flash. Signed-off-by: Grzegorz Bernacki <gjb@...> ---

This commits add library, which consist functions related creation/removal Secure Boot variables. Some of the functions was moved from SecureBootConfigImpl.c file. Signed-off-by: Grzegorz Bernacki

This commits add file which can be included by platform Flash Description File. It allows to specify certificate files, which will be embedded into binary file. The content of these files can be used