From: Peng Fan <peng.fan@oss.nxp.com>
To: John Ripple <john.ripple@keysight.com>
Cc: alexander.sverdlin@siemens.com, andrej.valek@siemens.com,
festevam@gmail.com, hs@denx.de, peng.fan@nxp.com,
sbabic@nabladev.com, sr@denx.de, trini@konsulko.com,
u-boot@lists.denx.de, uboot-imx@nxp.com
Subject: Re: [PATCH v3] imx8: Add ahab_commit command
Date: Tue, 9 Sep 2025 10:37:09 +0800 [thread overview]
Message-ID: <20250909023709.GA11150@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <20250908211838.3772709-1-john.ripple@keysight.com>
On Mon, Sep 08, 2025 at 03:18:38PM -0600, John Ripple wrote:
>The ahab_commit command allows the user to commit into the SECO fuses
>that control the SRK key revocation information. This is used to Revoke
>compromised SRK keys.
>
>To use ahab_commit, the boot container must be built with an SRK
>revocation bit mask that is not 0x0. For the SPSDK provided by NXP, this
>means setting the 'srk_revoke_mask' option in the config file used to
>sign the boot container. The 'ahab_commit 0x10' can then be used to commit
>the SRK revocation information into the SECO fuses.
>
>Signed-off-by: John Ripple <john.ripple@keysight.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2025-09-09 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 22:07 [PATCH] Add ahab_commit command for imx8 John Ripple
2025-07-15 3:47 ` Peng Fan
2025-08-15 16:49 ` [PATCH v2] imx8: " John Ripple
2025-08-18 4:33 ` Peng Fan
2025-08-18 15:43 ` [PATCH v2] imx8: Add ahab_commit command John Ripple
2025-09-08 21:18 ` [PATCH v3] " John Ripple
2025-09-09 2:37 ` Peng Fan [this message]
2025-09-09 19:53 ` [PATCH v4] " John Ripple
2025-09-09 5:11 ` [PATCH v3] " Heiko Schocher
2025-09-09 10:40 ` Fabio Estevam
2025-09-22 14:20 ` Fabio Estevam
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=20250909023709.GA11150@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.nxp.com \
--cc=alexander.sverdlin@siemens.com \
--cc=andrej.valek@siemens.com \
--cc=festevam@gmail.com \
--cc=hs@denx.de \
--cc=john.ripple@keysight.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@nabladev.com \
--cc=sr@denx.de \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox