Limiting the boot description to a fixed number of characters should be a platform policy. BDS common logic should NOT do that. Imagine a platform that contains a fancy UI with scrollbar or supports

Bob: Dose this change make FirmwareManagementProtocol to be used in runtime phase? Thanks Liming

You can create the PR by yourself. Thanks, Zhichao

Pierre: Can you submit BZ for this change request? Thanks Liming

Leif: I gave my Acked-by for this patch set V2. I think it can be merged now. Thanks Liming

Nah, I just folded it in. Pushed as 79019c7a4228..7ea7f9c07757. Thanks! (That ought to have been obvious even to me, oh well, thanks :) / Leif

Sorry I don't see it. Could you re-send it with "PATCH v2" in the subject line (by passing -v2 to "git format-patch") if you didn't already please? -- Rebecca Cran

Hi Rebecca, I think I already gave v2 an Acked-by, but just in case: Acked-by: Leif Lindholm <leif@...> Bob, Liming, Yuwei - any comments? / Leif Thu, Sep 23, 2021 at 10:09:55 -0600,

Linaro no longer do gcc releases - they're done by Arm now. Update gcc_aarch64_linux_ext_dep.yaml to fetch the latest AARCH64 gcc release (10.3-2021.07) from their site. Signed-off-by: Rebecca Cran

Linaro no longer do gcc releases - they're done by Arm now. Update gcc_arm_linux_ext_dep.yaml to fetch the latest ARM gcc release (10.3-2021.07) from their site. Signed-off-by: Rebecca Cran

BaseTools/Bin/gcc_[arm,aarch64]_linux_ext_dep.yaml downloads GCC releases from https://releases.linaro.org/components/toolchain/binaries/7.4-2019.02 . As indicated in the URL, those builds are from

That looks like something I missed and looks good, do you need me to make a v4 or will you just add that in. When I built I just used our application that has the guid in our inf so missed this. From

Hi Stefan, This patch looks good to me. Reviewed-by: Sami Mujawar <sami.mujawar@...> Regards, Sami Mujawar On 22/09/2021, 17:32, "Stefan Berger" <stefanb@...> wrote: From:

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3648 Register SmmExitBootServices and SmmLegacyBoot callback function to unregister this handler. Signed-off-by: Hao Shi <hao.shi@...> Cc:

REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3648 Register SmmExitBootServices and SmmLegacyBoot callback function to unregister this handler. Signed-off-by: Hao Shi <hao.shi@...> ---

REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3648 Register SmmExitBootServices and SmmLegacyBoot callback function to unregister this handler. Signed-off-by: Hao Shi <hao.shi@...>

HI Brijesh Thanks for the explanation. All fields in TDX metadata are required. So the current SEV proposal (3 fields) does not work for TDX. The extra fields are used to guide VMM on how to copy the

The discussion is in this link. https://edk2.groups.io/g/devel/message/80289

SEV hardware does not have a concept of the metadata. To boot SEV guest we need to pass some information to VMM and in past those information were passed through SNP_BOOT_BLOCK (GUIDed structure) but

Pushed as 8227e9e9f6a8. Thanks! / Leif