On 03/27/18 07:28, Andrew Fish wrote: > David, > > I'm not sure what you are asking? Per UEFI Spec boot policy there are > well know NVRAM variables that define boot policy. See UEFI Spec 3.3 > Globally Defined Variables. Look at BootOrder, BootNext, Boot#### etc. > > The memory mapped volume part is tricky as there is not a concept of > booting from a memory mapped volume. See "3.5 Boot Mechanisms" in the > UEFI Spec. > > If you loaded a RAM Disk driver that produced Simple File System then > you could form boot from that. The PI spec also defines how to load > something out of the FV, so it is also possible to boot from an FV via > a device path, but that is not mentioned in the UEFI Spec, as the PI > Spec is not required to implement UEFI.
edk2 also offers: MdeModulePkg/Universal/FvSimpleFileSystemDxe (Please see "FvSimpleFileSystemDxe.inf" for a description -- "Its primary intended use is to be able to start EFI applications embedded in FVs from the UEFI shell".) Thanks Laszlo >> On Mar 26, 2018, at 8:52 PM, david moheban <[email protected]> wrote: >> >> Hi, >> >> This question has always been very elusive despite hours of google >> searching. Was wondering how it would be possible to convert an efi program >> into a memory mapped volume that advertises itself onto your boot menu? For >> example to convert shell.efi into a bootable item on my boot menu. >> >> Thank you >> _______________________________________________ >> edk2-devel mailing list >> [email protected] >> https://lists.01.org/mailman/listinfo/edk2-devel > > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
