Hi Chandni, I have built and verified this patch and it looks good to me. Reviewed-by: Chris Jones <christopher.jones@...> Thanks, Chris

Hao,Can you give a R-b for this patch and the other one that changes PeiCore?

Thanks for all the valuable comments, Mario. I learned a lot from your comments. I just sent v4 for addressing your comments. By the way, forsamples/MinComm at develop · ms-iot/samples

This change is based on edk2-platforms-raspberrypi-pl011-bth-noflow.diff in https://github.com/worproject/RPi-Bluetooth-Testing/ with the modifications and additional changes below for enabling

Make the changes below for making it clearer. - Rename GpioPinSet() to GpioPinConfigure() - Rename parameter Val to Config and change its type to BOOLEAN Cc: Sami Mujawar

Changes: 1. Add code to ConfigDxe driver and AcpiTables module to dynamically build either Mini UART or PL011 UART info in ACPI. This also fixes the issue discussed in

In v4: Address comments given by Mario on v3. In v3: Address comments given by Jeremy, Mario, and Pete on v2. In v2: Address comments given by Pete on v1. Dynamically build UARTs info in ACPI so that

Hi Min M, I tested it with Ovmf. I will try other compiler and provide you logs soon. thanks, greg pt., 4 cze 2021 o 10:17 Xu, Min M <min.m.xu@...> napisał(a):

For my audio output protocol (I wonder if we should abbreviate it as AOP?) I need to get access to VirtIO devices in PCIe configuration space. However, I can't seem to find a way of telling QEMU to

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

I'll go with 3KB secrets + 1KB hashes. I'll go with the two GUIDed structures in the reset vector (which will point to distinct parts of a single 4KB page). That actually means shortening the

In our first version of TDVF, a static 5-level page table is used. It is simple and straight forward. But for *one binary* solution, we have to consider the compatibility with the current 4-level page

Secure Boot defines a security boundary between the firmware and the operating system: the operating system is not permitted to make arbitrary changes to firmware variables. It sounds as though you

The "one binary" decision isn't relevant here, is it? It would make more sense to implement 5-level paging within the base EDK2 architecture. This would allow that feature to be tested in

Continue my comments from here. It is because of the *one binary* so that we have to include all the drivers in the firmware binary. Some of the DXE drivers are not called in TDX, but they're

Leif and Bob: Thanks for your test and review. I create PR https://github.com/tianocore/edk2/pull/1690 for this patch. Thanks Liming to data. "); ");

Continue my comments from here. CFV is populated in post build. We can provide such python scripts to do the SB keys enrollment. As I mentioned above, SB keys are enrolled in post build phase. We

Reminder: TianoCore Design Meeting - APAC/NAMO When: 06/11/2021 9:30am to 10:30am (UTC+08:00) Asia/Shanghai Where: Microsoft Teams Organizer: Ray Ni ray.ni@... View

Hi Liming, Note - this does not only affect GCC49: it also affects at least GCC5 and CLANG38. This patch resolves the issue. Tested-by: Leif Lindholm <leif@...> (GCC49, GCC5,

Fix typographical error in the OvmfPkg/README by correcting the 'an' mistyped as 'and'. Cc: Ard Biesheuvel <ardb+tianocore@...> Cc: Jordan Justen <jordan.l.justen@...> Cc: