From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 4/4] Documentation: migration-guide: add note about ZynqMP OP-TEE
Date: Fri, 17 Apr 2026 10:52:27 +0200 [thread overview]
Message-ID: <20260417085235.3689546-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20260417085235.3689546-1-a.fatoum@pengutronix.de>
This popped up looking through AI-detected relevant device tree changes.
Assuming OP-TEE unconditionally was not a good idea anyways, so we won't
work around it and will just document this.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/migration-guides/migration-master.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
index 4a1de042d589..251e6f67d7b3 100644
--- a/Documentation/migration-guides/migration-master.rst
+++ b/Documentation/migration-guides/migration-master.rst
@@ -12,6 +12,15 @@ boards with the same binary.
The binary has been renamed from ``barebox-tqma8mpxl.img``
to ``barebox-tqma8mpxx.img``.
+ZynqMP
+^^^^^^
+
+The Linux v7.0 device trees imported into this barebox release no
+longer feature an unconditional `"linaro,optee-tz"` compatible OF node.
+
+If OP-TEE use in barebox is desired, this node must be added back to the
+barebox device tree.
+
HABv4-enablement
^^^^^^^^^^^^^^^^
--
2.47.3
next prev parent 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 ` [PATCH master 2/4] Documentation: migration-guide: reinstate HABv4-enablement Ahmad Fatoum
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 ` Ahmad Fatoum [this message]
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-4-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