From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH master] Documentation: migration-2025.05.0: document more changes
Date: Tue, 20 May 2025 10:47:01 +0200 [thread overview]
Message-ID: <20250520084701.703872-1-a.fatoum@barebox.org> (raw)
Looking through the git log for the next release shows some things,
users may stumble over when updating, so document them.
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
.../migration-guides/migration-2025.05.0.rst | 26 +++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/Documentation/migration-guides/migration-2025.05.0.rst b/Documentation/migration-guides/migration-2025.05.0.rst
index fe734a2921e5..82b9fcb8e53f 100644
--- a/Documentation/migration-guides/migration-2025.05.0.rst
+++ b/Documentation/migration-guides/migration-2025.05.0.rst
@@ -59,6 +59,16 @@ Board support
and using the hardware config FIP slot only as dummy.
See the lxa-tac board for an example.
+* ``barebox-sama5d27-som1-ek-xload-mmc.img`` has been renamed to
+ ``barebox-sama5d27-som1-ek-xload.img`` and
+ ``barebox-groboards-sama5d27-giantboard-xload-mmc.img`` has been renamed to
+ ``barebox-groboards-sama5d27-giantboard-xload.img`` to reflect
+ that the same image is now also bootable from QSPI flash.
+
+* Clock initialization for RK356x is no longer hardcoded, but is now
+ specified in the device tree. barebox device trees not including
+ ``#include rk356x.dtsi`` (in ``arch/arm/dts``) may regress.
+
Shell and magic variables
-------------------------
@@ -69,3 +79,19 @@ Shell and magic variables
This does not affect users setting ``nv boot.default``, but for
others, barebox will look for bootloader spec on the bootsource
medium first.
+
+Build system
+------------
+
+* When building for ``ARCH=sandbox``, ``libftdi1`` and ``sdl2``
+ libraries are now looked up with ``${CROSS_PKG_CONFIG}`` instead
+ of ``${PKG_CONFIG}``. This is not relevant when cross-building
+ just the barebox tools, which is the usual use case for sandbox
+ cross compilation.
+
+Bisectability
+-------------
+
+Many users of ``read*_poll_is_timeout`` are broken between
+``554bbc479c09..dea0ad02bbd6``, which can falsify git bisect
+results.
--
2.39.5
next reply other threads:[~2025-05-20 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 8:47 Ahmad Fatoum [this message]
2025-05-20 11:21 ` 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=20250520084701.703872-1-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--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