From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp,
quirin.gylstorff@siemens.com,
Shivanand.Kunijadar@toshiba-tsip.com
Subject: [isar-cip-core][PATCH 0/6] Enable SWUpdate support for bbb, update Isar
Date: Wed, 31 Aug 2022 09:31:15 +0200 [thread overview]
Message-ID: <cover.1661931081.git.jan.kiszka@siemens.com> (raw)
This primarily enables A/B rootfs SWUpdate for the BeagleBone Black, but
also updates the Isar revision and fixes an accidental host-side
dependency of the SWUpdate build.
Does anyone know how to make secure boot work with the BBB? Enabling the
software path should be just about building the needed config, but then
we still lack first-stage firmware validation by the hardware.
Next, it would be good to enable also a physical arm64 reference board
for SWUpdate. Any suggestions?
Jan
CC: dinesh.kumar@toshiba-tsip.com
CC: kazuhiro3.hayashi@toshiba.co.jp
CC: quirin.gylstorff@siemens.com
CC: Shivanand.Kunijadar@toshiba-tsip.com
Jan Kiszka (6):
swupdate: Use cpio from buildchroot
Update Isar revision
linux-cip: Update cip-kernel-config revision
u-boot-bbb: Switch BeagleBone Black to self-built U-Boot
swupdate: Drop u-boot-script from EFI Boot Guard images
Enable BeagleBone Black images with A/B SWUpdate support
Kconfig | 2 +-
classes/swupdate.bbclass | 53 ++++++++++---------
conf/machine/bbb.conf | 8 ++-
...ernel-Check-if-CONFIG_MODULES-is-set.patch | 33 ------------
kas-cip.yml | 6 +--
kas/opt/ebg-swu.yml | 1 +
recipes-bsp/u-boot/u-boot-bbb_2022.07.bb | 22 ++++++++
...boot-qemu-common.inc => u-boot-common.inc} | 11 ----
recipes-bsp/u-boot/u-boot-qemu-common.inc | 26 +--------
recipes-kernel/linux/linux-cip-common.inc | 2 +-
wic/bbb-efibootguard.wks.in | 21 ++++++++
wic/bbb.wks | 4 +-
12 files changed, 84 insertions(+), 105 deletions(-)
delete mode 100644 isar-patches/0001-recipes-kernel-Check-if-CONFIG_MODULES-is-set.patch
create mode 100644 recipes-bsp/u-boot/u-boot-bbb_2022.07.bb
copy recipes-bsp/u-boot/{u-boot-qemu-common.inc => u-boot-common.inc} (75%)
create mode 100644 wic/bbb-efibootguard.wks.in
--
2.35.3
next reply other threads:[~2022-08-31 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 7:31 Jan Kiszka [this message]
2022-08-31 7:31 ` [isar-cip-core][PATCH 1/6] swupdate: Use cpio from buildchroot Jan Kiszka
2022-08-31 7:31 ` [isar-cip-core][PATCH 2/6] Update Isar revision Jan Kiszka
2022-08-31 7:31 ` [isar-cip-core][PATCH 3/6] linux-cip: Update cip-kernel-config revision Jan Kiszka
2022-08-31 7:31 ` [isar-cip-core][PATCH 4/6] u-boot-bbb: Switch BeagleBone Black to self-built U-Boot Jan Kiszka
2022-08-31 7:31 ` [isar-cip-core][PATCH 5/6] swupdate: Drop u-boot-script from EFI Boot Guard images Jan Kiszka
2022-08-31 7:31 ` [isar-cip-core][PATCH 6/6] Enable BeagleBone Black images with A/B SWUpdate support 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.1661931081.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Shivanand.Kunijadar@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--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 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.