From: tho1.nguyendat@toshiba.co.jp
To: jan.kiszka@siemens.com, cip-dev@lists.cip-project.org
Cc: tho1.nguyendat@toshiba.co.jp, kazuhiro3.hayashi@toshiba.co.jp
Subject: [PATCH 2/3] bbb: Enable secured boot
Date: Mon, 28 Aug 2023 17:43:14 +0700 [thread overview]
Message-ID: <20230828104315.466393-3-tho1.nguyendat@toshiba.co.jp> (raw)
In-Reply-To: <20230828104315.466393-1-tho1.nguyendat@toshiba.co.jp>
From: Nguyen Dat Tho <tho1.nguyendat@toshiba.co.jp>
Signed-off-by: Nguyen Dat Tho <tho1.nguyendat@toshiba.co.jp>
---
Kconfig | 2 +-
wic/bbb-efibootguard-secureboot.wks.in | 13 +++++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
create mode 100644 wic/bbb-efibootguard-secureboot.wks.in
diff --git a/Kconfig b/Kconfig
index ec49631..3bbb5e3 100644
--- a/Kconfig
+++ b/Kconfig
@@ -190,7 +190,7 @@ config IMAGE_SWUPDATE
config IMAGE_SECURE_BOOT
bool "Secure boot support"
- depends on TARGET_QEMU_AMD64 || TARGET_QEMU_ARM64 || TARGET_QEMU_ARM
+ depends on TARGET_QEMU_AMD64 || TARGET_QEMU_ARM64 || TARGET_QEMU_ARM || TARGET_BBB
select IMAGE_SWUPDATE
config KAS_INCLUDE_SWUPDATE_SECBOOT
diff --git a/wic/bbb-efibootguard-secureboot.wks.in b/wic/bbb-efibootguard-secureboot.wks.in
new file mode 100644
index 0000000..504e2d8
--- /dev/null
+++ b/wic/bbb-efibootguard-secureboot.wks.in
@@ -0,0 +1,13 @@
+part --source rawcopy --sourceparams "file=/usr/lib/u-boot/bbb/MLO" --no-table --align 128
+part --source rawcopy --sourceparams "file=/usr/lib/u-boot/bbb/u-boot.img" --no-table --align 384
+
+include ebg-signed-sysparts.inc
+
+part --source rawcopy --sourceparams "file=${IMAGE_FULLNAME}.verity" --align 1024 --fixed-size 1G --uuid "${ABROOTFS_PART_UUID_A}"
+part --source empty --align 1024 --fixed-size 1G --uuid "${ABROOTFS_PART_UUID_B}"
+
+# home and var are extra partitions
+part /home --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/home --fstype=ext4 --label home --align 1024 --size 1G
+part /var --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/var --fstype=ext4 --label var --align 1024 --size 2G
+
+bootloader --ptable gpt --append="rootwait console=ttyO0,115200 omap_wdt.early_enable=1 omap_wdt.nowayout=1 watchdog.handle_boot_enabled=0"
--
2.39.2
next prev parent reply other threads:[~2023-08-28 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 10:43 [PATCH 0/3] Enable secured boot for BBB tho1.nguyendat
2023-08-28 10:43 ` [PATCH 1/3] linux/cip-kernel-config: Use latest commit tho1.nguyendat
2023-08-28 10:43 ` tho1.nguyendat [this message]
2023-08-28 10:43 ` [PATCH 3/3] u-boot: Add EFI secure boot dependency tho1.nguyendat
2023-08-28 12:45 ` [PATCH 0/3] Enable secured boot for BBB Jan Kiszka
2023-08-29 2:32 ` Trả lời: " tho1.nguyendat
2023-08-29 7:00 ` 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=20230828104315.466393-3-tho1.nguyendat@toshiba.co.jp \
--to=tho1.nguyendat@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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.