From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 16 Mar 2016 22:01:54 -0400 Subject: [U-Boot] [U-Boot,v6,19/30] efi_loader: Add "bootefi" command In-Reply-To: <1457566040-178816-1-git-send-email-agraf@suse.de> References: <1457566040-178816-1-git-send-email-agraf@suse.de> Message-ID: <20160317020154.GA23166@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Mar 10, 2016 at 12:27:20AM +0100, Alexander Graf wrote: > In order to execute an EFI application, we need to bridge the gap between > U-Boot's notion of executing images and EFI's notion of doing the same. > > The best path forward IMHO here is to stick completely to the way U-Boot > deals with payloads. You manually load them using whatever method to RAM > and then have a simple boot command to execute them. So in our case, you > would do > > # load mmc 0:1 $loadaddr grub.efi > # bootefi $loadaddr > > which then gets you into a grub shell. Fdt information known to U-boot > via the fdt addr command is also passed to the EFI payload. > > Signed-off-by: Alexander Graf > Reviewed-by: Simon Glass > Tested-by: Simon Glass Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: