I think this implementation guards against the possibility that you might have two similar devices that install the same third-party driver. Now the two drivers will install two HII forms with the sam

For example, writing a third-party driver (optionROM for a PCIe card). Using a varstore allows you to control how the configuration is stored and where it is stored - likely you have a config flash pa

Hi Konstantin, I could be wrong, but this is my understading of the situation. The process of building and using HII includes transpiling a file written in VFR into IFR bytecode. This transpilation is

Okay, I actually read the rest of your question and your problem is deeper than that. What you need is for the device to be connected to a driver (driver which might need to be loaded from the device

Hi, You can add a 'refreshguid' property to a number of VFR objects. Then, whenever you signal the event group with that guid, the object should be refreshed by the HII Browser. Cheers, Tom

Are you using Python 3? sandeep.dhanvada@...> wrote:

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 t

Hi Sandeep, You should probably discuss on this list what you want to add to the main tree before sending patches, you might get good pointers. Otherwise, there is a good guide as to how it works here

Hi Libo, The convention says that when a driver manages a device, it should find the relevant IO protocol installed on the device handle (for example a PCI device will have EFI_PCI_IO_PROTOCOL) and op

Hi Sandeep, Remind me, are you using a real platform to do these tests or are you using OVMF? If you are using real hardware, the platform needs to properly support capsules, which is quite rare unles

You can register your unload function in the .inf file for your driver like this: [Defines] ... UNLOAD_IMAGE = MyUnloadFunction

The difference between the 5.11 AMI bios and 4.654 AMI bios will be much, much bigger than just the difference between the spec revisions from 2.31 to 2.4. The spec revision is just the set of APIs th

You can register your unload function in the .inf file for your driver like this: [Defines] ... UNLOAD_IMAGE = MyUnloadFunction

I wouldn't be surprised if this was caused by improper memory management on unload (I actually wrote this kind of Highlander Protocol for the sfc driver). These are the things that I would check: 0. I

I wouldn't be surprised if this was caused by improper memory management on unload (I actually wrote this kind of Highlander Protocol for the sfc driver). This is what I would expect the driver to do:

HI Sandeep, The EsrtDxe provides an API to add ESRT entries manually, you could instrument that in SfcNicDriver actually - during controller binding check if gEsrtManagementProtocolGuid is installed a

Hi Sandeep, I suspect that if you include MdeModulePkg/Universal/EsrtFmpDxe module in the .dsc and .fdf file that you use to build the OVMF binaries, it might Just Work™. Cheers, Tom sandeep.dhanvada@

Hi Peter, This pair of options should do the trick: -drive if=pflash,format=raw,readonly,file=path/to/OVMF_CODE.fd -drive if=pflash,format=raw,file=path/to/OVMF_VARS.fd Note that the OVMF_CODE is moun

Hi Peter, I don’t recall a specific application-writer's-guide but the Driver Writer's Guide and the UEFI Specification are quite comprehensive. That said, you want to have a look at existing applicat

I had to solve this for myself by creating a PostReadyToBoot event that is signalled by my ReadyToBoot callback. That meant that my PostReadyToBoot callbacks got executed after all the ReadyToBoot eve