public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] efi_loader: PXE boot support
Date: Wed,  4 May 2016 19:10:49 +0200	[thread overview]
Message-ID: <1462381853-26828-1-git-send-email-agraf@suse.de> (raw)

One of the most common boot cases with EFI on arm64 is to boot from the
network using PXE boot. While TianoCore implements that just fine, we
were lacking support for it in U-Boot so far.

But no longer! Here is a patch set, enabling PXE booting of EFI payloads.
With this patch set, I was successfully able to automatically boot our
normal (usually used with TianoCore based systems) environment to boot
and run grub2 and a kernel from there with U-Boot.

Alexander Graf (4):
  efi_loader: Add network access support
  bootp: Move vendor class identifier set to function
  net: Move the VCI and client arch values to Kconfig
  distro: Add efi pxe boot code

 cmd/bootefi.c                          |   7 +
 configs/ls2080a_emu_defconfig          |   1 +
 configs/ls2080a_simu_defconfig         |   1 +
 configs/thunderx_88xx_defconfig        |   1 +
 configs/vexpress_aemv8a_dram_defconfig |   1 +
 configs/vexpress_aemv8a_juno_defconfig |   1 +
 configs/vexpress_aemv8a_semi_defconfig |   1 +
 configs/vexpress_ca15_tc2_defconfig    |   1 +
 configs/vexpress_ca5x2_defconfig       |   1 +
 configs/vexpress_ca9x4_defconfig       |   1 +
 include/config_distro_bootcmd.h        |  37 ++++-
 include/config_distro_defaults.h       |  21 ---
 include/configs/ls2080a_emu.h          |   1 -
 include/configs/ls2080a_simu.h         |   1 -
 include/configs/thunderx_88xx.h        |   2 -
 include/configs/vexpress_aemv8a.h      |   2 -
 include/configs/vexpress_ca15_tc2.h    |   1 -
 include/configs/vexpress_ca5x2.h       |   1 -
 include/configs/vexpress_ca9x4.h       |   1 -
 include/efi_api.h                      | 119 ++++++++++++++
 include/efi_loader.h                   |   7 +
 include/net.h                          |   2 +-
 lib/efi_loader/Makefile                |   1 +
 lib/efi_loader/efi_net.c               | 291 +++++++++++++++++++++++++++++++++
 net/Kconfig                            |  12 ++
 net/bootp.c                            |  37 +++--
 net/net.c                              |   4 +-
 net/tftp.c                             |   2 +
 28 files changed, 511 insertions(+), 47 deletions(-)
 create mode 100644 lib/efi_loader/efi_net.c

-- 
1.8.5.6

             reply	other threads:[~2016-05-04 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 17:10 Alexander Graf [this message]
2016-05-04 17:10 ` [U-Boot] [PATCH 1/4] efi_loader: Add network access support Alexander Graf
2016-05-04 17:10 ` [U-Boot] [PATCH 2/4] bootp: Move vendor class identifier set to function Alexander Graf
2016-05-06 17:48   ` Tom Rini
2016-05-04 17:10 ` [U-Boot] [PATCH 3/4] net: Move the VCI and client arch values to Kconfig Alexander Graf
2016-05-06 14:54   ` Tom Rini
2016-05-06 15:22     ` Alexander Graf
2016-05-06 15:38       ` Tom Rini
2016-05-06 16:07         ` Alexander Graf
2016-05-06 16:07     ` Leif Lindholm
2016-05-06 16:57       ` Tom Rini
2016-05-04 17:10 ` [U-Boot] [PATCH 4/4] distro: Add efi pxe boot code Alexander Graf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1462381853-26828-1-git-send-email-agraf@suse.de \
    --to=agraf@suse.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox