The problem is that there is no GUID for 'EFI_FILE_PROTOCOL' there's only 'EFI_SIMPLE_FILE_SYSTEM_PROTOCOL' which I already have.
I don't even understand the concept of a devicepath attached to a file since a file is not a device. How do the Shell or other boot manager load such files? On Fri, Feb 5, 2016 at 1:17 PM, Laszlo Ersek <ler...@redhat.com> wrote: > On 02/05/16 12:44, Michael Zimmermann wrote: > > Hi, > > > > how can I boot a EFI application if I have it's 'EFI_FILE_PROTOCOL'? > > 'BdsStartEfiApplication' does only accept a 'EFI_DEVICE_PATH'. > > You could do the following: > - call LocateHandle() to find all handles that have EFI_FILE_PROTOCOL > installed > - on each handle returned, call OpenProtocol() with GET_PROTOCOL and > the EFI_FILE_PROTOCOL GUID, and see if the returned protocol > interface address matches the one that you already have > - if so, call OpenProtocol() with GET_PROTOCOL and the > EFI_DEVICE_PATH_PROTOCOL GUID on the same handle. > > Laszlo > > > > > Michael > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > > > > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
