Hi All, I am a newbie in EFI development. Currently I have a requirement of enumerating attached USB devices, communicating with them and etc. However, after spending a day, I could not able to crack

What error did you get?

Hi, I've located a handle to the USB device with `gEfiSimpleFileSystemProtocolGuid.` Now I want to retrieve vendorID and productID with `gEfiUsbIoProtocolGuid,` and I got an error when trying to get

Reminder that the first Talkbox Office Day will be happening today! Here’s a new link in case the one below has expired! https://discord.gg/feYRkxz - Bret Sent: Friday, October 9, 2020 11:26

The Project Mu team is trying something a little new and different! In light of the limited involvement in UEFI and Tianocore community calls of late, we’re piloting a new idea for community

Thanks for the explanation, I got it now. Could you simply contribute the code to edk2 that you need in MdeModulePkg/Bus/Pci/NonDiscoverablePciDeviceDxe? If you add a new GUID and new branches in

What do you mean by "guids"? Did you mean "vendor id / device id" perhaps? Thanks Laszlo

We have a use case where we would want to expose PciIO protocols for a device that doesn't match any of the guids that it supports. Before we go and implement support for this wanted to get a feeling

Inline

I don't think you will be allowed to modify the DxeCapsuleLib to connect all controllers when it's loading the FMP embedded driver. There is probably a better way of doing it. Also, you need to send

Hi Tom, Please see the patches attached and let me know in case of any issues. I used all the "git config" options mentioned in the link you referred, but, I am not able to remove the line breaks at

Hi, (cross-posting to edk2-devel, comments below) OVMF does not contain an implementation of the EFI_MM_SW_DISPATCH_PROTOCOL. While OVMF does handle a particular software MMI, that handling

Wenyi, You can pass -n 1 to the edk2 build command to force a single threaded build to help debug compile issues. Thanks, Andrew Fish

Hey EfiSmmSwDispatch2Protocol is produced by a PchChildDispatch module on a real machine. There is no such protocol in OVMF environment, because it is emulated. I recommend you use

Hi, Trying to register a SMI in my custom SMM module I'm running into issues. Before registering the SMI, the code looks for the specific protocol this way: Status = gSmst->SmmLocateProtocol(

Hi, Trying to register a SMI in my custom SMM module I'm running into issues. Before registering the SMI, the code looks for the specific protocol this way: Status =

Hi, Trying to register a SMI in my custom SMM module here, and I'm running into an issue. Before registering the SMI, the code looks for the specific protocol this way: Status =

Yeah, I don't think this platform has any fancy way of doing this. Ah! Awesome, this was the bit I was missing! I suspect this is exactly what we are seeing. Since this board is in our LAVA farm