From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2B85C224AE8DE for ; Tue, 27 Mar 2018 02:18:13 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7AB45EB700; Tue, 27 Mar 2018 09:24:49 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-136.rdu2.redhat.com [10.10.120.136]) by smtp.corp.redhat.com (Postfix) with ESMTP id D2AF61C709; Tue, 27 Mar 2018 09:24:47 +0000 (UTC) To: david moheban Cc: Andrew Fish , "edk2-devel@lists.01.org" References: From: Laszlo Ersek Message-ID: Date: Tue, 27 Mar 2018 11:24:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Tue, 27 Mar 2018 09:24:49 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Tue, 27 Mar 2018 09:24:49 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:'' Subject: Re: How to make a memory mapped to FV ffs efi program? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 09:18:14 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 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 >> 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 >