From: Yao Zi <me@ziyao.cc>
To: Junhui Liu <junhui.liu@pigmoral.tech>, u-boot@lists.u-boot-project.org
Cc: Tom Rini <trini@konsulko.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Simon Glass <sjg@chromium.org>,
Daniel Golle <daniel@makrotopia.org>, Randolph Sapp <rs@ti.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Kory Maincent <kory.maincent@bootlin.com>,
E Shattow <e@freeshell.de>, Yixun Lan <dlan@kernel.org>,
spacemit@lists.linux.dev, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v2 1/2] tools: mkimage: add SpacemiT K3 boot image support
Date: Thu, 10 Sep 2026 12:35:26 +0000 [thread overview]
Message-ID: <aqKkDoGgnJkOQ8s-@pie> (raw)
In-Reply-To: <20260909-spacemit-aihd-v2-1-780e98cf2fec@pigmoral.tech>
On Wed, Sep 09, 2026 at 11:51:08PM +0800, Junhui Liu wrote:
> The SpacemiT BootROM loads the FSBL from a boot image consisting of a
> fixed 4 KiB header with two metadata headers and authentication
> information, followed by a 32-byte-aligned SPL payload and a trailing
> authentication area. K1 and K3 share the same layout, but use different
> integrity and authentication schemes. K1 requires RSA-signed images,
> while K3 uses CRC32 to verify images in non-secure boot mode.
>
> Add mkimage type "smtimage" for the K3 CRC32 path. Populate both
> metadata headers, fill their CRC32 values and the payload CRC32, and
> reserve the authentication areas required by the layout.
>
> The image header has no reliable K1/K3 identifier, so select the SoC
> with -n. Omit dumpimage support since it cannot take -n to distinguish
> between the variants.
>
> Only "-n k3" in non-secure boot mode is supported. Route SoC differences
> through a variant table so K1 and RSA authentication support can be
> added later.
>
> Tested-by: E Shattow <e@freeshell.de>
> Signed-off-by: Junhui Liu <junhui.liu@pigmoral.tech>
> ---
> boot/image.c | 1 +
> include/image.h | 1 +
> tools/Makefile | 1 +
> tools/smtimage.c | 202 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 205 insertions(+)
...
> diff --git a/tools/smtimage.c b/tools/smtimage.c
> new file mode 100644
> index 000000000000..96e8b5d8d171
> --- /dev/null
> +++ b/tools/smtimage.c
...
> +#include <image.h>
> +#include <u-boot/crc.h>
> +#include "imagetool.h"
I think you should explicitly include all headers you used explicitly,
e.g., string.h for strcmp(), stdint.h for uintXX_t...
...
> +static const struct smtimage_variant *smtimage_get_variant(const char *name)
> +{
> + int i;
> +
> + if (!name || !*name)
> + return NULL;
Isn't this !*name check unnecessary?
> +
> + for (i = 0; i < ARRAY_SIZE(smtimage_variants); i++)
> + if (!strcmp(name, smtimage_variants[i].name))
> + return &smtimage_variants[i];
> +
> + return NULL;
> +}
Regards,
Yao Zi
next prev parent reply other threads:[~2026-09-10 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 15:51 [PATCH v2 0/2] tools: mkimage: add SpacemiT K3 boot image support Junhui Liu
2026-09-09 15:51 ` [PATCH v2 1/2] " Junhui Liu
2026-09-10 10:02 ` Yixun Lan
2026-09-10 12:35 ` Yao Zi [this message]
2026-09-09 15:51 ` [PATCH v2 2/2] doc: board: spacemit: document the SpacemiT boot image format Junhui Liu
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=aqKkDoGgnJkOQ8s-@pie \
--to=me@ziyao.cc \
--cc=daniel@makrotopia.org \
--cc=dlan@kernel.org \
--cc=e@freeshell.de \
--cc=ilias.apalodimas@linaro.org \
--cc=junhui.liu@pigmoral.tech \
--cc=kory.maincent@bootlin.com \
--cc=quentin.schulz@cherry.de \
--cc=rs@ti.com \
--cc=sjg@chromium.org \
--cc=spacemit@lists.linux.dev \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox