Hii all,
I have 2 questions:
1. The uefi screen that shows up in qemu, which I got from the edk2
website, has:
Continue
Select Language
Boot Manager
Device Manager
Boot Maintenance Manager
When I develop a driver with HII support, I can view my forms and
configurations in the Device Manager.
However, when I boot from different systems, like vmware that have made their
own uefi support, the screen does not contain the Device Manager option. So it
doesn't seem I can even browse my HII forms there.
How then can I browse my forms in this situation?
2. I see this code in DriverSampleDxe from edk2:
Status = gBS->InstallMultipleProtocolInterfaces (
&DriverHandle,
&gEfiDevicePathProtocolGuid,
&mHiiVendorDevicePath0,
&gEfiHiiConfigAccessProtocolGuid,
&PrivateData->ConfigAccess,
NULL
);
I am wondering what the EfiDevicePathProtocol is used for?
I tried commenting out the lines for it (&gEfiDevicePathProtocolGuid &
&mHiiVendorDevicePath0)
It compiles fine and runs fine, but when I try to browse the forms (using the
device manager option from the uefi in qemu) it will freeze and not load the
forms.
Why is this Device Path Protocol needed in order for the HII forms to load?
Thanks, Ben S.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
