From: Jon Mason <jon.mason@arm.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH 2/2] arm-bsp/tc1: re-enable signed kernel image
Date: Wed, 24 May 2023 11:02:37 -0500 [thread overview]
Message-ID: <20230524160237.3275001-2-jon.mason@arm.com> (raw)
In-Reply-To: <20230524160237.3275001-1-jon.mason@arm.com>
---
meta-arm-bsp/conf/machine/include/tc.inc | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/meta-arm-bsp/conf/machine/include/tc.inc b/meta-arm-bsp/conf/machine/include/tc.inc
index 14ec7205..75bfea07 100644
--- a/meta-arm-bsp/conf/machine/include/tc.inc
+++ b/meta-arm-bsp/conf/machine/include/tc.inc
@@ -10,6 +10,17 @@ UBOOT_RD_LOADADDRESS = "0x88000000"
UBOOT_RD_ENTRYPOINT = "0x88000000"
UBOOT_LOADADDRESS = "0x80080000"
UBOOT_ENTRYPOINT = "0x80080000"
+# Below options will generate a key to sign the kernel Image and INITRAMFS_IMAGE
+# according to the default parameters of kernel-fitimage.bbclass. If the user
+# would prefer to use their own keys, disable the key generation using the
+# FIT_GENERATE_KEYS parameter and specify the location of the keys using the
+# below paramters.
+UBOOT_SIGN_ENABLE = "1"
+UBOOT_MKIMAGE_DTCOPTS = "-I dts -O dtb"
+UBOOT_SIGN_KEYNAME = "dev_key"
+UBOOT_SIGN_KEYDIR = "${DEPLOY_DIR_IMAGE}/keys"
+FIT_GENERATE_KEYS = "1"
+FIT_SIGN_INDIVIDUAL = "1"
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
--
2.30.2
next prev parent reply other threads:[~2023-05-24 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 16:02 [PATCH 1/2] arm-bsp/tc1: use latest kernel and u-boot Jon Mason
2023-05-24 16:02 ` Jon Mason [this message]
2023-05-25 0:51 ` [PATCH 2/2] arm-bsp/tc1: re-enable signed kernel image Jon Mason
2023-05-25 6:50 ` [meta-arm] [PATCH 1/2] arm-bsp/tc1: use latest kernel and u-boot Mikko Rapeli
2023-05-25 11:41 ` Ross Burton
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=20230524160237.3275001-2-jon.mason@arm.com \
--to=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
/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.