Makes sense. Let's go with the branch. Mike: yes, that was what I was suggesting wrt cherry-picking and pushing. Best Regards, Leif

FWIW, we tried both branches and tags in Mu, and have gotten more mileage out of branches. We will still do tags periodically (to establish a point at which all the sub repos were put through a full

Hi Leif, I think you are suggesting that a local branch could be created from edk2-stable202011 and the 2 commits cherry-picked onto that local branch and then create a tag on that local branch

Hi Mike, This looks fine to me. I will add a potential tweak that I won't strongly advocate for, but think should be considered: We don't technically need a branch for this; a tag could be

Hello, The following bug has been fixed on edk2/master https://bugzilla.tianocore.org/show_bug.cgi?id=3111 https://github.com/tianocore/edk2/pull/1226 This bug is also considered a critical

Besides document, we filed below EDKII Bugzilla during code revisit: 3087 EDK2 Code unassigned@... UNCO --- TCG: EFI_EXIT_BOOT_SERVICES_INVOCATION is not recorded when ExitBootService

Responsive to Jiewen's message below one can find "Understanding the Trusted Boot Chain Implementation" at the following links: HTML:

Currently, RngDxe in SecurityPkg only supports Intel, with RdRand support. This RFC is to start a discussion about adding support for ARM. I have a Git branch with support for the optional ARMv8.5

Maybe you can upload the content to https://edk2.groups.io/g/devel/files/Designs, where we hold the design review ppt, etc. I assume we want to discuss below two APIs implementation, right? 1)

Hi Sami, JPGs work, but preferably published in a location where they're unlikely to be deleted, and posted as URLs. https://app.diagrams.net/ doesn't require a licensed application to edit, and can

Hi All, I am working on the TRNG FW API interface and will share more details for the discussion soon. We had some thoughts about streamlining the RngDxe implementations and would like to share some

There is also the TRNG FW API, which is an architected SMC firmware interface: https://developer.arm.com/documentation/den0098/latest/ ________________________________ Sent: Tuesday, December 8,

Good suggestion. Thanks Dick. Vincent and I have plan to refresh our TPM2 whitepaper recently. We will definitely take it into consideration, to add more detail on describing the EDK2 intent and

[RFC] The code that creates the TCG Event Log needs an audit Problem Statement The TCG support code included in the EDK2 tree is in place to enable the two major features provided by a platform TPM.

Hi Everyone, This RFC has been sitting for a while and it seems like we have reached a conclusion. I would like to make a request to the TianoCore stewards to create 2 new git repositories in the

In order to support Intel Trust Domain Extensions (TDX) (https://software.intel.com/content/www/us/en/develop/articles/intel-trust-domain-extensions.html), we need a new Trust Domain Virtual Firmware

Could you explain more about the gap that needs to be bridged here? I suppose the desire is to be able to reuse existing DXE_SMM_DRIVER modules, and deploy them unmodified in a standalone MM

Hi, Sami I know the traditional MM is planned to be deprecated but the reality is that there are many existing traditional MM platforms/drivers and the migration has to happen step-by-step. It may

Hi Siyuan, I can see the following points: - current code organisation is such that the traditional MM and standalone MM are clearly separated. - traditional MM is planned to be deprecated. - some