Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jamin Lin <jamin_lin@aspeedtech.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <troy_lee@aspeedtech.com>, <jamin_lin@aspeedtech.com>
Subject: [PATCH v2 0/3] Support signing U-Boot FIT image without SPL
Date: Tue, 17 Jun 2025 16:10:49 +0800	[thread overview]
Message-ID: <20250617081052.3087995-1-jamin_lin@aspeedtech.com> (raw)

v1:
- uboot-sign: Make SPL DTB public key injection optional

v2:
- Fix review issue
- Add test for signing U-Boot FIT image without SPL
- Refactor condition checks to use && and || instead of -a and -o
- Support signing U-Boot FIT image without SPL
  - The `SPL_DTB_BINARY` variable can be explicitly set to an empty string
    to indicate that no SPL is present.
  - The signing logic checks `SPL_DTB_BINARY` and skips injecting the
    key or verifying the SPL DTB if it is empty.
  - The FIT image generation and deployment are always performed if
    `UBOOT_FITIMAGE_ENABLE` is enabled, regardless of the SPL settings.

Jamin Lin (3):
  uboot-sign: Support signing U-Boot FIT image without SPL
  uboot-sign.bbclass: Refactor condition checks to use && and || instead
    of -a and -o
  oe-selftest: fitimage: Add test for signing U-Boot FIT image without
    SPL

 meta/classes-recipe/uboot-sign.bbclass   | 74 ++++++++++++++----------
 meta/lib/oeqa/selftest/cases/fitimage.py | 37 ++++++++++++
 2 files changed, 79 insertions(+), 32 deletions(-)

-- 
2.43.0



             reply	other threads:[~2025-06-17  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  8:10 Jamin Lin [this message]
2025-06-17  8:10 ` [PATCH v2 1/3] uboot-sign: Support signing U-Boot FIT image without SPL Jamin Lin
2025-06-17  8:10 ` [PATCH v2 2/3] uboot-sign.bbclass: Refactor condition checks to use && and || instead of -a and -o Jamin Lin
2025-06-17  8:10 ` [PATCH v2 3/3] oe-selftest: fitimage: Add test for signing U-Boot FIT image without SPL Jamin Lin

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=20250617081052.3087995-1-jamin_lin@aspeedtech.com \
    --to=jamin_lin@aspeedtech.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=troy_lee@aspeedtech.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