From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] fixup! ARM: i.MX: karo-tx6: use mmcboot handler
Date: Tue, 21 Oct 2025 17:27:50 +0200 [thread overview]
Message-ID: <20251021152753.1357904-1-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20251021144106.1228193-2-f.pfitzner@pengutronix.de>
Documentation: migration-2025.11.0: mention Karo bbu change
The existing method of hardcoding boot0 is not power-fail safe, so it's
hopefully not used by userspace to update the bootloader, but in any
case a warning sounds apt.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.../migration-guides/migration-2025.11.0.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst
index 9cbc46acc39b..a9c7abb66ef0 100644
--- a/Documentation/migration-guides/migration-2025.11.0.rst
+++ b/Documentation/migration-guides/migration-2025.11.0.rst
@@ -1,3 +1,6 @@
+Release v2025.11.0
+==================
+
i.MX GPIOs
----------
@@ -5,3 +8,13 @@ Reading output GPIOs now returns the configured output level instead
of reading back the input register. This aligns us with what Linux
is doing, but may falsify readings of single-ended GPIOs that have
the SION bit configured.
+
+Board support
+-------------
+
+Karo TX6X
+^^^^^^^^^
+
+The barebox update handler for this SoM no longer unconditionally updates
+/dev/mmc3.boot0, but instead it now updates the inactive boot partition
+on /dev/mmc3 and then sets it as active allowing for power-fail safety.
--
2.47.3
next prev parent reply other threads:[~2025-10-21 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 14:41 [PATCH] " Fabian Pfitzner
2025-10-21 15:27 ` Ahmad Fatoum [this message]
2025-10-21 15:28 ` Ahmad Fatoum
2025-10-22 6:30 ` 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=20251021152753.1357904-1-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