All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Lukasz Majewski <lukma@nabladev.com>
Cc: Stefano Babic <sbabic@nabladev.com>,
	Fabio Estevam <festevam@gmail.com>,
	uboot-imx@nxp.com, u-boot@lists.denx.de,
	John Ripple <john.ripple@keysight.com>,
	Peng Fan <peng.fan@nxp.com>, Ji Luo <ji.luo@nxp.com>
Subject: Re: [PATCH] arm: imx: Add command to get offset of first image in AHAB OS container
Date: Mon, 10 Nov 2025 08:53:50 -0600	[thread overview]
Message-ID: <20251110145350.GK6688@bill-the-cat> (raw)
In-Reply-To: <20251110124100.4193259-1-lukma@nabladev.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Mon, Nov 10, 2025 at 01:41:00PM +0100, Lukasz Majewski wrote:

> With current mainline it is possible to check with AHAB if system OS image
> can be trusted (with 'auth_cntr' command).
> However, after the validation one needs to use the image (fitImage in this
> case) itself. Such operation requires getting the offset in the image
> eligible for AHAB validation to start execution of the fitImage.
> 
> Command in this patch allows it, so with:
> auth_cntr_offset ${addr} auth_cntr_os_offset;
> setexpr addr ${kernel_addr_r} + ${auth_cntr_os_offset};
> 
> it is possible to boot the fitImage after AHAB IP block vaidation.
> 
> Signed-off-by: Lukasz Majewski <lukma@nabladev.com>
> ---
>  arch/arm/mach-imx/imx8/ahab.c | 50 +++++++++++++++++++++++++++++++++++
>  1 file changed, 50 insertions(+)

Can we please split the commands here out and put it under
cmd/imx/imxh-ahab.c or something? Thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-10 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 12:41 [PATCH] arm: imx: Add command to get offset of first image in AHAB OS container Lukasz Majewski
2025-11-10 14:53 ` Tom Rini [this message]
2025-11-10 19:14   ` Łukasz Majewski

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=20251110145350.GK6688@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=festevam@gmail.com \
    --cc=ji.luo@nxp.com \
    --cc=john.ripple@keysight.com \
    --cc=lukma@nabladev.com \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@nabladev.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.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.