From: Jan Kiszka <jan.kiszka@siemens.com>
To: <cip-dev@lists.cip-project.org>
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: [isar-cip-core][PATCH 0/4] Fix EFI Boot Guard for aarch64
Date: Mon, 21 Mar 2022 08:59:16 +0100 [thread overview]
Message-ID: <cover.1647849560.git.jan.kiszka@siemens.com> (raw)
This is unfortunately not yet stressed in isar-cip-core itself (someone
should add a non-secure SWUpdate via U-Boot UEFI first), so it was only
found while trying to enable a layer that uses isar-cip-core. But to
move forward, I'm pushing the fixes already.
Jan
Jan Kiszka (4):
shtab: Fix cross build
shtab: Fix PYBUILD_NAME
efibootguard: Fix non-x86 builds
efibootguard: Fix plugins for aarch64
recipes-bsp/efibootguard/efibootguard_0.10.bb | 17 +++++++++--
.../0001-configure-Fix-aarch64-EFI-arch.patch | 28 +++++++++++++++++++
....install => efibootguard-dev.install.tmpl} | 3 +-
recipes-python/shtab/files/rules | 2 +-
recipes-python/shtab/python3-shtab_1.4.2.bb | 2 +-
.../wic/plugins/source/efibootguard-boot.py | 11 ++++++--
.../wic/plugins/source/efibootguard-efi.py | 2 +-
7 files changed, 55 insertions(+), 10 deletions(-)
create mode 100644 recipes-bsp/efibootguard/files/0001-configure-Fix-aarch64-EFI-arch.patch
rename recipes-bsp/efibootguard/files/debian/{efibootguard-dev.install => efibootguard-dev.install.tmpl} (50%)
--
2.34.1
next reply other threads:[~2022-03-21 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 7:59 Jan Kiszka [this message]
2022-03-21 7:59 ` [isar-cip-core][PATCH 1/4] shtab: Fix cross build Jan Kiszka
2022-03-21 7:59 ` [isar-cip-core][PATCH 2/4] shtab: Fix PYBUILD_NAME Jan Kiszka
2022-03-21 7:59 ` [isar-cip-core][PATCH 3/4] efibootguard: Fix non-x86 builds Jan Kiszka
2022-03-21 7:59 ` [isar-cip-core][PATCH 4/4] efibootguard: Fix plugins for aarch64 Jan Kiszka
2022-03-21 12:32 ` [isar-cip-core v2][PATCH " Jan Kiszka
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=cover.1647849560.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=quirin.gylstorff@siemens.com \
/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