All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nishanth Menon" <nm@ti.com>
To: <praneeth@ti.com>
Cc: <denis@denix.org>, <meta-ti@lists.yoctoproject.org>,
	Nishanth Menon <nm@ti.com>
Subject: [dunfell/master][PATCH 1/7] conf/machine: k3: Add multi-certificate boot image support
Date: Wed, 31 Mar 2021 11:51:27 -0500	[thread overview]
Message-ID: <20210331165133.3746-2-nm@ti.com> (raw)
In-Reply-To: <20210331165133.3746-1-nm@ti.com>

Lets keep things consistent by providing two possibilities for platforms
to pick from - legacy boot and multi-certificate boot.

In legacy boot, the base bootloader and system firmware are
maintained as separate binaries (tiboot3.bin and sysfw.itb).

In multi-certificate boot that newer K3 devices support, ROM is smarter
and can handle multiple x509 certificate based images: so we can strip
out the sysfw.itb and integrate it as part of tiboot3.bin itself. This
improves authentication and overall system boot times since we are now
able to boot both the system controller and the boot processor in
parallel.

We do have a scheme currently to identify the images necessary for boot
etc, but things are handled on a platform conf file basis. We can
improve that by introducing the pattern at the top level include and use
the relevant pattern in platforms as needed.

Signed-off-by: Nishanth Menon <nm@ti.com>
---
 conf/machine/include/k3.inc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
index c727d724ac28..56ad40c3f963 100644
--- a/conf/machine/include/k3.inc
+++ b/conf/machine/include/k3.inc
@@ -40,7 +40,11 @@ MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2 alsa ethernet pci"
 
 IMAGE_FSTYPES += "tar.xz wic.xz"
 
-IMAGE_BOOT_FILES ?= "${SPL_BINARY} u-boot.${UBOOT_SUFFIX} tiboot3.bin sysfw.itb"
+IMAGE_BOOT_FILES_LEGACY = "${SPL_BINARY} u-boot.${UBOOT_SUFFIX} tiboot3.bin sysfw.itb"
+IMAGE_BOOT_FILES_MULTI_CERT = "${SPL_BINARY} u-boot.${UBOOT_SUFFIX} tiboot3.bin"
+
+IMAGE_BOOT_FILES ?= "${IMAGE_BOOT_FILES_LEGACY}"
+
 WKS_FILE ?= "sdimage-2part.wks"
 do_image_wic[depends] += "virtual/bootloader:do_deploy"
 do_image_wic[mcdepends] += "mc::k3r5:virtual/bootloader:do_deploy mc::k3r5:ti-sci-fw:do_deploy"
-- 
2.31.0


  reply	other threads:[~2021-03-31 16:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 16:51 [dunfell/master][PATCH 0/7] conf/machine: k3: cleanup wic files Nishanth Menon
2021-03-31 16:51 ` Nishanth Menon [this message]
2021-03-31 22:19   ` [dunfell/master][PATCH 1/7] conf/machine: k3: Add multi-certificate boot image support Denys Dmytriyenko
2021-03-31 16:51 ` [dunfell/master][PATCH 2/7] conf/machine: am65xx: Document boot images as legacy mode Nishanth Menon
2021-03-31 22:23   ` Denys Dmytriyenko
2021-03-31 23:57     ` Nishanth Menon
2021-03-31 16:51 ` [dunfell/master][PATCH 3/7] conf/machine: j7: " Nishanth Menon
2021-03-31 22:24   ` Denys Dmytriyenko
2021-03-31 16:51 ` [dunfell/master][PATCH 4/7] conf/machine: j7200-evm: Switch to multi-certificate boot images Nishanth Menon
2021-03-31 22:30   ` Denys Dmytriyenko
2021-03-31 16:51 ` [dunfell/master][PATCH 5/7] conf/machine: am64xx: Consolidate image configuration to SoC include Nishanth Menon
2021-03-31 22:33   ` Denys Dmytriyenko
2021-03-31 23:56     ` Nishanth Menon
2021-03-31 16:51 ` [dunfell/master][PATCH 6/7] conf/machine: am64xx: Switch to multi-certificate boot images Nishanth Menon
2021-03-31 22:35   ` Denys Dmytriyenko
     [not found]   ` <16718E3613B720CC.10817@lists.yoctoproject.org>
2021-03-31 22:35     ` [meta-ti] " Denys Dmytriyenko
2021-03-31 23:55       ` Nishanth Menon
2021-03-31 16:51 ` [dunfell/master][PATCH 7/7] conf/machine: k3: Lets build bmap files by default Nishanth Menon
2021-03-31 22:44   ` Denys Dmytriyenko

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=20210331165133.3746-2-nm@ti.com \
    --to=nm@ti.com \
    --cc=denis@denix.org \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=praneeth@ti.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.