v2025.09.0 has been released and it contained multiple things worthy of a migration notes entry. Add them now.
Cc: Sascha Hauer <[email protected]> Cc: Marco Felsch <[email protected]> Signed-off-by: Ahmad Fatoum <[email protected]> --- @Sascha, @Marco, please check if I got the details right. Please try to update the migration guide yourselves when doing similarly breaking changes in future. Thanks. Signed-off-by: Ahmad Fatoum <[email protected]> --- Documentation/migration-guides/index.rst | 6 ++-- .../migration-guides/migration-2025.09.0.rst | 33 +++++++++++++++++++ 2 files changed, 35 insertions(+), 4 deletions(-) create mode 100644 Documentation/migration-guides/migration-2025.09.0.rst diff --git a/Documentation/migration-guides/index.rst b/Documentation/migration-guides/index.rst index 2dfa7f05bb40..a04b2b07c4d3 100644 --- a/Documentation/migration-guides/index.rst +++ b/Documentation/migration-guides/index.rst @@ -9,8 +9,6 @@ configuration and downstream board support. barebox API breakage that cause build errors are generally out-of-scope for these documents. .. toctree:: + :glob: - migration-2025.05.0 - migration-2025.06.0 - migration-2025.07.0 - migration-2025.08.0 + migration-20* diff --git a/Documentation/migration-guides/migration-2025.09.0.rst b/Documentation/migration-guides/migration-2025.09.0.rst new file mode 100644 index 000000000000..f432991449e9 --- /dev/null +++ b/Documentation/migration-guides/migration-2025.09.0.rst @@ -0,0 +1,33 @@ +Release v2025.09.0 +================== + +Removal of CONFIG_BOOTM_FITIMAGE_PUBKEY +--------------------------------------- + +The legacy way of adding FIT keys to the barebox build was having mkimage +generate a device tree snippet and including it in the barebox board device +tree:: + +#ifdef CONFIG_BOOTM_FITIMAGE_PUBKEY +#include CONFIG_BOOTM_FITIMAGE_PUBKEY +#endif + +This has now been removed in favor of ``CONFIG_CRYPTO_PUBLIC_KEYS``. +This option doesn't consume device tree snippets, but file paths to +the PEM or PKCS#11 URIs and thus will require a build-time OpenSSL dependency. + +Build dependencies +------------------ + +* Building barebox for 64-bit Rockchip platforms required OpenSSL v3.0 or later. + This was unintended and the fix is queued for v2025.10.0. + +* ti-linux-firmware 11.00.14 renames ``ti-fs-firmware-am62lx-hs-fs-enc.bin`` to + to ``ti-fs-firmware-am62lx-hs-enc.bin`` and ``ti-fs-firmware-am62lx-hs-fs-cert.bin`` + is renamed to ``ti-fs-firmware-am62lx-hs-cert.bin`` and barebox has followed suit. + +Rename in /dev +-------------- + +EEPROMs that are pointed at by a device tree alias do no longer have +an extra 0 at the end, e.g., ``/dev/eeprom00`` has become ``/dev/eeprom0``. -- 2.47.3
