On Jun 24, 2013, at 11:28 AM, Laszlo Ersek <[email protected]> wrote:
> IIRC Andrew may have stated at one point that *some* shell is required > at all times for fundamental UEFI functionality. The shell is a UEFI application, and DOES NOT produce anything fundamental to UEFI functionality. The shell just consumes UEFI functionality. There are some things, like volume names, that don't exist in UEFI that the shell "invents". So if you application is using a shell invention, buy definition it depends on the shell to provide that service. I think we have also commented in the past that the shell will ASSERT if it loads on a pre UEFI 2.3 (don't remember the exact version) system. The shell, like any UEFI application, can figure out where it was booted from so if the shell is making assumptions about booting from a filesystem it is likely a bug in the shell. Thanks, Andrew Fish > What you're seeing > could be per-design. (I only use Shell2 as PXE payload because PXE boot > is easy to verify with it; my OVMF.fd usually embeds Shell1.) ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
