Hi Lior Thanks a lot for getting back to me. This is part of the EFI_FILE_PROTOCOL: https://uefi.org/specs/UEFI/2.10/13_Protocols_Media_Access.html#efi-file-protocol EFI_FILE_PROTOCOL.Open()

Could this be the case that your module/driver is getting loaded before some other Protocol you are using have been created/registered?

Hello, I am interested into asking a question if anyone knows how an application in the Runtime OS, can transfer some data (an array of characters for example) into the Smm side, by making use of

Hello Peter, Probably 'EFI_UNSUPPORTED' means that there is no driver on the system that handles the protocol.If that is the case, try to load a driver that supports this protocol, using the load

Try posting it on the 'devel' group

Konstantin: I have reviewed all patches except for BaseTools: Add support for SUBTYPE_GUID section generation. I include Bob to review this change. If I miss some one, please let me know.

Peter, I'm not sure what programming environment or API you're using... it would help if you could report what UEFI protocols are being used at the bottom of your implementation. "root->OpenEx()" is

People don't really answer here it seems to such requests because it may rather be about development and not for support. Not sure if there is a better community for uefi issues. Let me know if you

In 'MdeModulePkg\Bus\I2c\I2cDxe', since the following protocol is not installed: gEfiI2cMasterProtocolGuid gEfiI2cEnumerateProtocolGuid gEfiI2cBusConfigurationManagementProtocolGuid So I refer to the

I am wondering if this is the right mailing list to discuss my issue. If it is not, please let me know the right list to send my question, thanks!

Hello, I'm Martin and I'm the author of the patch proposing adding SBOM information to the EFI binaries during the building [1]. We (with Richard Hughes from LVFS) joined one of the

Dear EDK2 community We're developing an application and need to write asynchronously to disk. This fails on all machines we are using with the error message EFI_UNSUPPORTED. Maybe you can help in

Hi, I am building OVMF.fd for X64, and can load it in Qemu, and can confirm everything works, including running my simple Helloworld.efi from UEFI shell in Qemu. However, I notice that OVMF does not

Konstantin: I have reviewed some patches of you. I will review the remaining patches this week, merge them if no more comments. Thanks Liming

You followed the correct process. I've found that patches _do_ sometimes just get ignored/forgotten, and months later I've had to follow up about them. I'm hoping the move to GitHub Pull Requests will

Hello! I'm experiencing some difficulties in getting maintainers' attention to my EDKII patches. Some of the patches I've created at the end of july, now it is the end of september, so I'm a little

Hello! I was investigating the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL and it looks like the syntax for the <KeywordRequest> listed in the UEFI specification is not fully supported. (Unified Extensible

Many Thanks Andrew Clear now Regards Kumar

Kumar, Yes this is kind of the definition of cooperative. No cooperation == deadlock. If you notice the UEFI Spec claims the TPL_HIGH_LEVEL is reserved for the system firmware. There is no need for

Many Thanks for reply Andrew, Sorry it brings a couple of questions. may be stupid questions cooperative event model. running. execution will never run again. dispatched when calling