On 1 February 2016 at 19:45, Alexander Graf <ag...@suse.de> 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 <ag...@suse.de> > Reviewed-by: Simon Glass <s...@chromium.org> > > --- > > v1 -> v2: > > - Move to GPLv2+ > > v2 -> v3: > > - Move to new cmd directory > - Add kconfig option > - Fix comment style > - Add help text > - s/-1/-ENOENT > - Move obj list to lib > > XXX bootefi: make dtb conf table more explicit > --- > cmd/Kconfig | 7 +++ > cmd/Makefile | 1 + > cmd/bootefi.c | 167 > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 175 insertions(+) > create mode 100644 cmd/bootefi.c
Tested on Beaglebone Black and Minnowboard MAX: Tested-by: Simon Glass <s...@chromium.org> _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot