The build step can refer to https://github.com/tianocore/tianocore.github.io/wiki/CLANG9-Tools-Chain#the-verbos-build-and-run-steps-in-windows This step is to build EDK2 with CLANGPDB tool chain.

Hello, Do we have steps to build the latest EDK II source? or any related reference link? Also can we build EDK II source without MS VisualStudio being installed in the system? In my windows machine,

Your "trick" is undefined behavior. EFI_SIMPLE_TEXT_INPUT_PROTOCOL is not a runtime protocol; you cannot use it after ExitBootServices(). TBH I don't understand your purpose. Why do you call

Hello, I am an amateur. I made a uefi app for reading some type of images (bmp os/2) and files in folders. That also provides mice and keyboard support. I did not use edk2 but gnu-efi later I will

It was very helpful. Thank you for your kindness!

This applies only to drivers that do not follow the UEFI Driver Model (considering the protocols that expose the driver's actual business). NvmExpressDxe is a UEFI_DRIVER that follows the UEFI Driver

https://github.com/tianocore/edk2-platforms/commit/8dd78ea11a38d2d7e8031c4783e9f2ca5569956b That was indeed the problem. I changed the RPI4 platform code to always connect to devices and regenerate

Hello Laszlo, Thank you sincerely! It works just as you said! Snippet: https://gist.github.com/jc-lab/e9c019b8f5c220d06fe312c9bf3af350 Thanks Jospeh.

Hello Laszlo, It has not been checked in detail, but my predictions are this. 1. When a driver is loaded, it calls "InstallMultipleProtocolInterfaces" within that driver. 2. In this process,

I don't understand "installing the driver". Also, what is "notify" in this context? Do you mean the RegisterProtocolNotify() boot service? In what context are you trying to use it? The BDS phase is

Hello Laszlo, Thanks for your answer. I looked at this a bit more today. The cause is not that there is no driver, but it seems that Notify does not work properly for the protocol after installing

Dropping <joseph@...> from the address list, because the RH SMTP server keeps telling me that the domain for that email address (i.e., "zeronsoftn.com") is unidentifiable. Comments

Hello, Some computers (what I checked was an LG laptop) do not recognize the NVMe SSD as a block device in the EFI program. Of course, the OS on the NVMe SSD is bootable. But when I boot with

Hi Laszlo Ersek, Thanks for the style comments, I appreciate it, I will do these changes. And, for the questions, I agree, for the first question, that seems to be a platform driver bug and, for the

Style comment: you should remove "gPciIo", and use the auto-generated "gEfiPciIoProtocolGuid" variable instead. Why not read it with a single EfiPciIoWidthUint16 operation? Also, for the offset,

Hello, I am learning about PCI and trying to write an application that lists PCI controllers in UEFI environment, using EFI_PCI_IO_PROTOCOL and EDK2. I want to list some information from

Hi, I was trying to build the UEFI-SCT for EDK2 on my windows box running cygwin. I follow edk2-test/uefi-sct/HowToBuild/How to build SCT.txt for build instruction. It says X64 is unsupported

Right, my apologies. I'm not sure why I wrote CloseProtocol(). Perhaps a typo, or maybe I lost track of where I was in the PDF with "evince". That seems to be the case, yes. Agreed. Laszlo

Thank you! I see that text in the documentation for the deprecated call UninstallProtocolInterface(), which explains why I hadn't previously noticed it. Based on what the EDK2 implementation

The CloseProtocol() specification has parts as follows (relevant passage is the last one below): The caller is responsible for ensuring that there are no references to a protocol interface