From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Graf <agraf@suse.de>
Date: Wed, 13 Apr 2016 21:01:17 +0200
Subject: [U-Boot] efi_loader: Add distro boot script for removable media
In-Reply-To: <570E95FD.402@suse.de>
References: <570E87D1.7050603@wwwdotorg.org> <570E8ECA.3010103@suse.de>
 <570E9091.7060203@wwwdotorg.org> <570E944D.1050507@suse.de>
 <570E95FD.402@suse.de>
Message-ID: <570E977D.6070208@suse.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



On 13.04.16 20:54, Andreas F?rber wrote:
> Am 13.04.2016 um 20:47 schrieb Alexander Graf:
>>   load mmc 0 $fdt_addr_r my_awesome.dtb ;\
>>   load mmc 0 $kernel_addr_r some/random/path/grub2.efi ;\
>>   bootefi $kernel_addr_r
> 
> If we're going in that direction, I would rather pass $fdt_addr_r as
> second optional argument to bootefi. That would be more consistent with
> bootm, bootz, booti.

Yes, probably.

> While at it, is there a reason that bootz/booti create some output about
> memory locations of initrd/fdt but bootefi does not?

Is that important information? I don't quite get the feeling that it is.


Alex