mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 2/4] Documentation: migration-guide: reinstate HABv4-enablement
Date: Fri, 17 Apr 2026 10:52:25 +0200	[thread overview]
Message-ID: <20260417085235.3689546-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20260417085235.3689546-1-a.fatoum@pengutronix.de>

This got dropped inadvertently. Restore it as the upcoming release will
be the first to include it.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/migration-guides/migration-master.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
index 32813ed7da2b..3fad2f1053c6 100644
--- a/Documentation/migration-guides/migration-master.rst
+++ b/Documentation/migration-guides/migration-master.rst
@@ -11,3 +11,9 @@ The config option has been renamed from ``CONFIG_MACH_TQ_MBA8MPXL`` to
 boards with the same binary.
 The binary has been renamed from ``barebox-tqma8mpxl.img``
 to ``barebox-tqma8mpxx.img``.
+
+HABv4-enablement
+^^^^^^^^^^^^^^^^
+
+When the SRK hash is written, the corresponding fuse bank is now locked automatically.
+With that the ``IMX_SRK_HASH_WRITE_LOCK`` flag is removed.
-- 
2.47.3




  reply	other threads:[~2026-04-17  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  8:52 [PATCH master 1/4] Documentation: migration-guide: fix TQMA8MPxL section Ahmad Fatoum
2026-04-17  8:52 ` Ahmad Fatoum [this message]
2026-04-17  8:52 ` [PATCH master 3/4] Documentation: migration-guide: mention TF-A v2.14 compatibility Ahmad Fatoum
2026-04-17  8:52 ` [PATCH master 4/4] Documentation: migration-guide: add note about ZynqMP OP-TEE Ahmad Fatoum
2026-04-17 10:43 ` [PATCH master 1/4] Documentation: migration-guide: fix TQMA8MPxL section Sascha Hauer

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=20260417085235.3689546-2-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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