From: Jamin Lin <jamin_lin@aspeedtech.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <troy_lee@aspeedtech.com>, <jamin_lin@aspeedtech.com>
Subject: [PATCH v5 0/3] uboot-sign: support ATF and TFE ITS generation
Date: Wed, 11 Dec 2024 10:35:12 +0800 [thread overview]
Message-ID: <20241211023515.2108415-1-jamin_lin@aspeedtech.com> (raw)
v0:
1. add variable to set load address and entrypoint.
2. Fix to install nonexistent dtb file.
3. support to verify signed FIT
4. support to load optee-os and TFA images
v1:
Fix patch for code review
v2:
created a series patch
v3:
add cover letter
v4:
Add oe-self testcases for reviewer suggestion
Add documentation for reviewer suggestion.
Link: https://patchwork.yoctoproject.org/project/docs/patch/20241118062113.269253-1-jamin_lin@aspeedtech.com/
The following patches had been applied from v0 changes.
a. Fix to install nonexistent dtb file
b. support to verify signed FIT
c. add variable to set load address and entrypoint.
v5:
1. create a new variable to add users snippet ITS.
2. remove uboot_fitimage_user_image hook function
Jamin Lin (3):
uboot-sign: support to create TEE and ATF image tree source
uboot-sign: support to add users specific image tree source
oe-selftest: fitimage: add testcases to test ATF and TEE
meta/classes-recipe/uboot-sign.bbclass | 96 +++++++-
meta/lib/oeqa/selftest/cases/fitimage.py | 288 +++++++++++++++++++++++
2 files changed, 383 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2024-12-11 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 2:35 Jamin Lin [this message]
2024-12-11 2:35 ` [PATCH v5 1/3] uboot-sign: support to create TEE and ATF image tree source Jamin Lin
2024-12-11 2:35 ` [PATCH v5 2/3] uboot-sign: support to add users specific " Jamin Lin
2024-12-11 2:35 ` [PATCH v5 3/3] oe-selftest: fitimage: add testcases to test ATF and TEE Jamin Lin
2025-01-02 2:41 ` [PATCH v5 0/3] uboot-sign: support ATF and TFE ITS generation 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=20241211023515.2108415-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 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.