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 3E6F021EB528D for ; Tue, 27 Mar 2018 05:21: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 BC6C4722C5; Tue, 27 Mar 2018 12:27: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 4812150331; Tue, 27 Mar 2018 12:27:49 +0000 (UTC) To: david moheban References: From: Laszlo Ersek Cc: edk2-devel@lists.01.org Message-ID: Date: Tue, 27 Mar 2018 14:27:48 +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.2]); Tue, 27 Mar 2018 12:27:49 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Tue, 27 Mar 2018 12:27: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 12:21:14 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 03/27/18 13:43, david moheban wrote: > I was just curious on how certain firmware packages take a Efi Shell > and make it available to boot from the F8 or F11 (or whatever) boot > menu. I suppose to make your own you have to write a dxe driver that > adds the location via guid to the boot menu? Almost. In edk2 platforms, the agent that does this is usually not a separate DXE driver, but the given platform's PlatformBootManagerLib instance, which is linked into, and called from, BdsDxe. For two examples, please see PlatformRegisterFvBootOption() in: - ArmVirtPkg/Library/PlatformBootManagerLib/PlatformBm.c - OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c A related function is RemoveStaleFvFileOptions(), in both. Thanks Laszlo