From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] bootefi fixes for aarch64/layerscape
Date: Thu, 14 May 2020 14:38:27 +0200 [thread overview]
Message-ID: <20200514123831.30157-1-michael@walle.cc> (raw)
I'm bringing up efiboot on a ARM64 board which runs without TF-a and PSCI,
therefore the secondary cores are brought up by spin-tables. I ran into
several problems. Here are the fixes.
Michael Walle (4):
efi_loader: aarch64: align runtime section to 64kb
efi_loader: check alignment in efi_add_memory_map()
fsl-layerscape: align first parameter of efi_add_memory_map()
efi_loader: call smp_kick_all_cpus()
arch/arm/cpu/armv8/fsl-layerscape/fdt.c | 2 +-
arch/arm/cpu/armv8/u-boot.lds | 9 ++++++++-
common/bootm.c | 9 +++++++++
lib/efi_loader/efi_memory.c | 18 +++++-------------
lib/efi_loader/efi_setup.c | 6 ++++++
5 files changed, 29 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2020-05-14 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:38 Michael Walle [this message]
2020-05-14 12:38 ` [PATCH 1/4] efi_loader: aarch64: align runtime section to 64kb Michael Walle
2020-05-14 18:27 ` Heinrich Schuchardt
2020-05-14 19:04 ` Michael Walle
2020-05-14 21:03 ` Heinrich Schuchardt
2020-05-14 22:02 ` Michael Walle
2020-05-14 22:27 ` Heinrich Schuchardt
2020-05-14 23:04 ` Heinrich Schuchardt
2020-05-15 11:39 ` Michael Walle
2020-05-28 17:11 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 2/4] efi_loader: check alignment in efi_add_memory_map() Michael Walle
2020-05-14 18:35 ` Heinrich Schuchardt
2020-05-14 18:50 ` Michael Walle
2020-05-14 22:02 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 3/4] fsl-layerscape: align first parameter of efi_add_memory_map() Michael Walle
2020-05-14 18:39 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 4/4] efi_loader: call smp_kick_all_cpus() Michael Walle
2020-05-14 18:46 ` Heinrich Schuchardt
2020-05-14 20:17 ` Alexander Graf
2020-05-14 20:35 ` Michael Walle
2020-05-16 15:54 ` Michael Walle
2020-05-18 18:30 ` Tom Rini
2020-05-18 18:45 ` Heinrich Schuchardt
2020-05-18 19:23 ` Tom Rini
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=20200514123831.30157-1-michael@walle.cc \
--to=michael@walle.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.