Hi, I don't have a stake in this feature, but because the presentation isn't long, I've briefly skimmed it: - It's unclear whether the public data structures describe a wire format. If they do, they

Dandan, The Status Code Protocol/PPI is the high-level interface which is being implemented.  The ReportStatusCodeRouter module implements this in terms of the ReportStatusCodeHandler

Friendly reminder to review and provide feedback on the RFC. We are looking to target a WW34 deadline with this design. Best, Curtis

Hi, I filed a proposal for a new library to handle UEFI BIOS sub-regions athttps://bugzilla.tianocore.org/show_bug.cgi?id=2808. Attached is a slide deck with design overview of the new library.

Hi Sahil, Your proposal interests us too. I got a question for you. Are you planning to use or leverage SPCI library interfaces for interaction between OP-TEE and Standalone MM?

Hm... OK. Thanks Laszlo

Hi Brian, Personally, I prefer to add the NULL class Library to StatusCodeHandler modules. 1. I think we should make the functionality of each module clear and separated. It may also be why we

Sent: Saturday, June 20, 2020 1:29 AM To: devel@edk2.groups.io; Bi, Dandan <dandan.bi@...>; rfc@edk2.groups.io Cc: Dong, Eric <eric.dong@...>; Ni, Ray <ray.ni@...>; Wang, Jian J

I think the need to execute from ROM makes this tricky. It looks to me that it is easy to move from PCD to libs for the StatusCodeHandler since registration is basically `RscHandlerPpi->Register

Dandan, We'll have a lot of layers of indirection....  The ReportStatusCodeRouter modules will call one or more StatusCodeHandlerModules, and the standard StatusCodeHandler modules will call

So I assume you're going to remove PcdStatusCodeUseSerial and PcdStatusCodeUseMemory, and when converting the existent platforms, the new NULL class resolutions in the DSC files will reflect the

Hi All, REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2816 We plan to separate two kinds of NULL class libraries for Memory and serial handlers from

Leif, I received additional feedback on this proposal. We should add the UEFI Shell Specification to this new process. This includes adding a bugzilla.tianocore.org product category and a new Github

Rebecca, I was able to confirm that it was an issue with Git for Windows. Looks like it’s fixed in current snapshots and will be in the next

That's different -- in this case, peer certificate verification was attempted, but it failed, because the root certificate in the peer's cert chain is not trusted by your system (your openSUSE WSL

That’s not a bad idea: I should try with my WSL install. I’m on the same version of Git for Windows, and think I’ll open it as an issue to the maintainer. For now, going though the paces is

Rebecca, I cheated and used smtpServer = relay.apple.com and smtpEncryption = tls. Seems relay.apple.com does not require authentication and it just worked. I used an internal git mailing list to

I'm getting the same error, but with a different packaging of Git: mine's in C:\Program Files\Git\cmd\git.exe . It's version "git version 2.26.2.windows.1". Of course it's possible it's just the

I think your perl installation and your git installation may come from different sources, and the perl install may not satisfy the git install's dependencies. In GNU/Linux distribution lingo, I'd