Or an EFI System Configuration table (which uses a GUID to identify it) Not sure about SSDT, since that would require an AML interpreter.
Tim -----Original Message----- From: H. Peter Anvin [mailto:h...@zytor.com] Sent: Thursday, April 04, 2013 4:50 PM To: edk2-devel@lists.sourceforge.net Cc: Tim Lewis Subject: Re: [edk2] Boot to ISO image in volatile memory On 04/04/2013 12:27 PM, Tim Lewis wrote: > Produce an instance of BLOCK_IO protocol which returns pieces of the > in-memory image. Then perform a ConnectController() on that handle, which > should cause a DISK_IO and SIMPLE_FILE_SYSTEM to be mounted automatically. > > Then, you use the file system to load the boot loader (LoadImage()), signal > the ready-to-boot event, set up the UEFI watchdog timer, and then start the > boot loader (StartImage()). There may be a few more standard boot items I may > be forgetting, but that's about it. > > Tim For the record, it is a *very* frequent request in Linux circles to enable a standard way for the OS to find such an image. The obvious way is via an ACPI SSDT. -hpa ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
