Zephyr 4.0 module update overview

[dkalowsk]

Umbrella issue for modules which may require an update before Zephyr 4.0.

• https://github.com/zephyrproject-rtos/acpica (@najumon1980)
• https://github.com/zephyrproject-rtos/babblesim-manifest (@aescolar) (manifest: Update bsim to version v2.4 #80510)
• https://github.com/zephyrproject-rtos/canopennode (@henrikbrixandersen)
• https://github.com/zephyrproject-rtos/chre (@yperess)
• https://github.com/zephyrproject-rtos/cmsis (@stephanosio, @microbuilder, @povergoing)
• https://github.com/zephyrproject-rtos/cmsis-dsp (@XenuIsWatching, @stephanosio) (manifest: update cmsis-dsp to v1.16.2 #80495)
• https://github.com/zephyrproject-rtos/cmsis-nn (@XenuIsWatching, @stephanosio)
• https://github.com/zephyrproject-rtos/edtt (@aescolar, @wopu-ot, @thoh-ot)
• https://github.com/zephyrproject-rtos/fatfs (@de-nordic)
• https://github.com/zephyrproject-rtos/hostap (@krish2718, @jukkar)
• https://github.com/zephyrproject-rtos/liblc3 (@Casper-Bonde-Bose, @MariuszSkamra)
• https://github.com/zephyrproject-rtos/libmetal (@carlocaione, @arnopo)
• https://github.com/zephyrproject-rtos/littlefs (???)
• https://github.com/zephyrproject-rtos/loramac-node (@Mani-Sadhasivam)
• https://github.com/zephyrproject-rtos/lvgl (@faxe1008, @brgl, @pdgendt)
• https://github.com/zephyrproject-rtos/lz4 (@parthitce )
• https://github.com/zephyrproject-rtos/mcuboot (@d3zd3z, @de-nordic, @nordicjm)
• https://github.com/zephyrproject-rtos/nanopb (@pdgendt) (submanifests: optional: Bump nanopb to 0.4.9 #80555)
• https://github.com/zephyrproject-rtos/open-amp (@carlocaione)
• https://github.com/zephyrproject-rtos/openthread (@rlubos)
• https://github.com/zephyrproject-rtos/percepio (@eriktamlin, @aronlander-pe)
• https://github.com/zephyrproject-rtos/picolibc (@keith-packard, @stephanosio)
• https://github.com/zephyrproject-rtos/sof (@kv2019i)
• https://github.com/zephyrproject-rtos/tflite-micro (@laurenmurphyx64)
• https://github.com/zephyrproject-rtos/thrift (@cfriedt)
• https://github.com/zephyrproject-rtos/zcbor (@de-nordic)
• https://github.com/zephyrproject-rtos/zephyr-lang-rust (@d3zd3z)
• https://github.com/zephyrproject-rtos/zscilib (@microbuilder)

Folks that are tagged please comment and confirm the status of your modules with respect to readiness for the 4.0 release.

• Zephyr 4.0 Release Checklist #76338
• Zephyr 4.0 security related modules update overview #80489

[aescolar]

@dkalowsk EDTT is already the latest version. For bsim / Babblesim, I just qeued a PR with a minor update with some minor improvements. It is not required for 4.0 but does not harm either.

[henrikbrixandersen]

@dkalowsk CANopenNode will not be updated before v4.0 (tracked here: #70285).

[jukkar]

@dkalowsk hostap update is planned after 4.0 is released (tracked in Wi-Fi project page Wi-Fi)

[faxe1008]

@dkalowsk LVGL will updated after 4.0.

[XenuIsWatching]

@dkalowsk CMSIS-NN is already at the latest version, there was no new tag since then
CMSIS-DSP will be updated to 1.16.2#80495

[microbuilder]

There is a PR for zscilib, but waiting on the PR author to comment, and can be updated post 4.0 release.

[keith-packard]

In picolibc, there are some fixes for clang, arc and xtensa upstream which should probably get pulled in for 4.0. We'll need to sync with the SDK and see when that might get updated.

[stephanosio]

In picolibc, there are some fixes for clang, arc and xtensa upstream which should probably get pulled in for 4.0. We'll need to sync with the SDK and see when that might get updated.

@keith-packard Unless those are critical bug fixes, we will likely have to target 4.1 since releasing and integrating another version of SDK will likely take more than a week and, at that point, we will be at rc2 or even rc3 where we cannot risk toolchain-related regressions.

[stephanosio]

CMSIS (v5) is already at the latest version (5.9.0). As for CMSIS v6, it will likely have to be added as a separate module: #77220.

[keith-packard]

@keith-packard Unless those are critical bug fixes, we will likely have to target 4.1 since releasing and integrating another version of SDK will likely take more than a week and, at that point, we will be at rc2 or even rc3 where we cannot risk toolchain-related regressions.

Sounds fine -- none of them are critical.