Bernd Kuhls
52f46b24ef
package/python-flask: security bump version to 3.1.3
...
https://github.com/pallets/flask/blob/3.1.3/CHANGES.rst
Fixes CVE-2026-27205: https://nvd.nist.gov/vuln/detail/CVE-2026-27205
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
eafd8fb98d
package/python-filelock: bump version to 3.25.2
...
https://github.com/tox-dev/filelock/blob/3.25.2/docs/changelog.rst
Upstream switched license to MIT:
4aac7862f5
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
d92aa484d7
package/python-fastapi: bump version to 0.135.1
...
https://github.com/fastapi/fastapi/blob/0.135.1/docs/en/docs/release-notes.md
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
1adf7b961b
package/python-evdev: bump version to 1.9.3
...
https://python-evdev.readthedocs.io/en/latest/changelog.html#feb-05-2025
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
4c5aae676b
package/python-dbus-fast: bump version to 4.0.0
...
https://github.com/Bluetooth-Devices/dbus-fast/releases/tag/v4.0.0
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
8d0906b77f
package/python-cssselect2: bump version to 0.9.0
...
https://github.com/Kozea/cssselect2/releases/tag/0.9.0
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
9b0a90c10c
package/python-cssselect: bump version to 1.4.0
...
https://github.com/scrapy/cssselect/blob/v1.4.0/CHANGES
"Switched the build system to ``hatchling``."
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:19 +01:00
Bernd Kuhls
e3fee9b098
package/python-charset-normalizer: bump version to 3.4.5
...
https://github.com/jawah/charset_normalizer/blob/3.4.5/CHANGELOG.md
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
81541039cd
package/python-certifi: bump version to 2026.2.25
...
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
904e49a795
package/python-botocore: bump to version 1.42.68
...
https://github.com/boto/botocore/blob/1.42.68/CHANGELOG.rst
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
9beb705fc4
package/python-boto3: bump version to 1.42.68
...
https://github.com/boto/boto3/blob/1.42.68/CHANGELOG.rst
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
09299bc551
package/python-bitstring: bump version to 4.4.0
...
https://github.com/scott-griffiths/bitstring/blob/4.4.0/release_notes.md
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
69b36ebac9
package/python-async-lru: bump version to 2.2.0
...
https://github.com/aio-libs/async-lru/blob/v2.2.0/CHANGES.rst
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
44c2393af9
package/python-apispec: bump version to 6.10.0
...
https://github.com/marshmallow-code/apispec/blob/6.10.0/CHANGELOG.rst
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
bdacb1a483
package/python-aiorwlock: bump version to 1.5.1
...
https://github.com/aio-libs/aiorwlock/blob/v1.5.1/CHANGES.rst
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
9e08e5029f
package/python-aiomqtt: bump version to 2.5.1
...
https://github.com/empicano/aiomqtt/blob/v2.5.1/CHANGELOG.md
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
5e49c6e18b
package/python-aenum: bump version to 3.1.16
...
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Bernd Kuhls
808bb5fea3
package/python-hatchling: bump version to 1.29.0
...
https://github.com/pypa/hatch/blob/hatchling-v1.29.0/docs/history/hatchling.md
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 16:21:18 +01:00
Dowan Gullient
86d453a7dc
toolchain/toolchain-external/toolchain-external-arm-arm: bump to 15.2.rel1
...
Update the ARM external toolchain to the latest 15.2.rel1
release from ARM.
This involves:
- Updating the version, site URL, and source filename in .mk
- Updating the SHA256 hash in .hash
- Updating the display name and GCC version dependency in Config.in
Verified by booting on a default Qemu configuration.
Signed-off-by: Dowan Gullient <dowan.gullient@smile.fr >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 14:22:08 +01:00
Dowan Gullient
8cb765faa6
toolchain/toolchain-external/toolchain-external-arm-aarch64-be: bump to 15.2.rel1
...
Update the ARM aarch64-be external toolchains to the latest 15.2.rel1
release from ARM.
This involves:
- Updating the version, site URL, and source filename in .mk
- Updating the SHA256 hash in .hash
- Updating the display name and GCC version dependency in Config.in
Signed-off-by: Dowan Gullient <dowan.gullient@smile.fr >
[Julien: add newline at end of file to fix check-package error]
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 14:21:59 +01:00
Dowan Gullient
8d413d6179
toolchain/toolchain-external/toolchain-external-arm-aarch64: bump to 15.2.rel1
...
Update the ARM aarch64 external toolchain to the latest 15.2.rel1
release from ARM.
This involves:
- Updating the version, site URL, and source filename in .mk
- Updating the SHA256 hash in .hash
- Updating the display name and GCC version dependency in Config.in
Verified by booting on a default Qemu configuration.
Signed-off-by: Dowan Gullient <dowan.gullient@smile.fr >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 14:17:00 +01:00
Bernd Kuhls
2ee9ccae5d
{linux, linux-headers}: bump 6.{12, 18, 19}.x series
...
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 11:28:09 +01:00
Bernd Kuhls
171d4d489c
package/sqlite: bump version to 3.51.3
...
https://sqlite.org/releaselog/3_51_3.html
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 11:20:05 +01:00
Bernd Kuhls
04473f5559
Revert "package/sqlite: bump version to 3.52.0"
...
This reverts commit 04dbf7a38f .
Upstream withdrew this release:
https://www.sqlite.org/releaselog/3_52_0.html
"Due to backwards-compatibility issues associated with some new
features, the 3.52.0 release has been withdrawn."
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-15 11:20:04 +01:00
Bernd Kuhls
2e2d038918
package/xz: bump version to 5.8.2
...
https://github.com/tukaani-project/xz/releases/tag/v5.8.2
"- Fix the build on ARM64 on glibc versions older than
2.24 (2016). They don't have HWCAP_CRC32 in <sys/auxv.h>."
Updated license hashes due to upstream commit
6d287a3ae9
Fixes:
https://autobuild.buildroot.net/results/b0d/b0dbae7b2c884f5fef0017755b28932a83921a5a/
"check/crc32_arm64.h:27:25: fatal error: sys/auxv.h: No such file or directory
27 | # include <sys/auxv.h>"
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 23:20:32 +01:00
Bernd Kuhls
bdeb0d0a32
package/flashrom: bump version to 1.7.0
...
https://github.com/flashrom/flashrom/blob/v1.7.0/doc/release_notes/v_1_6.rst
https://github.com/flashrom/flashrom/blob/v1.7.0/doc/release_notes/v_1_7.rst
Renamed license file and updated license hash due to upstream commit:
4b370bebb7
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 22:57:02 +01:00
Bernd Kuhls
cc80c55415
package/dos2unix: bump version to 7.5.4
...
https://waterlan.home.xs4all.nl/dos2unix/ChangeLog.txt
Updated license hash due to copyright year bump:
0ab159a6c8 /
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 22:48:56 +01:00
Bernd Kuhls
b38ef052d6
package/file: bump version to 5.47
...
https://github.com/file/file/blob/FILE5_47/ChangeLog
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 21:59:03 +01:00
Bernd Kuhls
66b617af7b
package/iwd: bump version to 3.12
...
https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/ChangeLog?h=3.12
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 21:38:16 +01:00
Bernd Kuhls
9b839527e3
package/ell: bump version to 0.83
...
https://git.kernel.org/pub/scm/libs/ell/ell.git/tree/ChangeLog?h=0.83
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 21:38:15 +01:00
Bernd Kuhls
4d4dc5f542
package/libxml2: security bump version to 2.15.2
...
Release notes:
https://download.gnome.org/sources/libxml2/2.15/libxml2-2.15.2.news
- CVE-2026-1757 fix: Memory leak in xmllint Shell - shell.c
- CVE-2026-0990 fix: Prevent infinite recursion in
xmlCatalogListXMLResolve
- CVE-2026-0992 fix: Exponential behavior when handling
- parser: Fix infinite loop in xmlCtxtParseContent
- CVE-2025-10911 libxslt related: Ignore next/prev of documents when
traversing XPath
- CVE-2026-0989 fix: Add RelaxNG include limit
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-14 21:23:44 +01:00
Julien Olivain
c1bc1a7a61
support/testing: fs: new xfs runtime test
...
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:30:06 +01:00
Julien Olivain
ffaccc4ccc
fs/xfs: add support for generating a xfs image
...
mkfs.xfs is able to populate a filesystem from a directory since
upstream commit [1], included since v6.17.
With this option, it is now possible to create XFS rootfs in
Buildroot. This commit adds this new feature.
[1] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=8a4ea72724930cfe262ccda03028264e1a81b145
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:30:02 +01:00
Julien Olivain
45a74068df
package/xfsprogs: enable host package variant
...
The host mkfs.xfs is needed to create XFS root filesystems
in Buildroot.
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:29:59 +01:00
Julien Olivain
9af1a2bd07
package/liburcu: enable host package variant
...
host-liburcu is needed for host-xfsprogs.
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:29:56 +01:00
Julien Olivain
5e0ab7e9eb
package/inih: enable host package variant
...
host-inih is needed for host-xfsprogs.
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:29:53 +01:00
Julien Olivain
3ce11070cb
package/xfsprogs: bump version to 6.18.0
...
Changelog:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/tree/doc/CHANGES?h=v6.18.0
This commit refreshes the patch 0001 (rebase and update upstream link
to lore mailing list). It also removes the patch 0002 included in
this new version and removes the corresponding _AUTORECONF and
_POST_CONFIGURE_HOOKS.
Also, the upstream commit [1] introduced a usage of the "capacity"
field of zoned block devices, introduced in Kernel commit [2],
first included in v5.9. For this reason, this commit adds the new
dependency to BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_9.
For that reason, this commit updates the test_xfsprogs runtime test
to switch to a Bootlin external toolchain, which includes Kernel
headers that meet this new requirement.
Finally, this commit also updates this runtime test Kernel version
to the LTS 6.18.9. This is because the default filesystem options
of mkfs.xfs were updated in upstream commit [3] to include new
features supported in the new Kernel 6.18.y LTS series. The commit [3]
is included in xfsprogs v6.18.
[1] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=48ccc2459039309cfbaf358febea53a86f07827c
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82394db7383d33641f3f565bd79792fb41b1741f
[3] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=54aad16b4b9b923442b4042afaba4438ca1aa868
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:29:49 +01:00
Julien Olivain
c03712d8ec
support/testing: test_xfsprogs: use bootlin toolchain, update kernel
...
This commit updates the test configuration to switch to a Bootlin
external toolchain. This is needed to get newer toolchain kernel
headers required by newer xfsprogs versions.
xfsprogs upstream commit [1] (included in v6.15) introduced a usage
of the "capacity" field of zoned block devices, introduced in Kernel
commit [2], first included in v5.9.
This commit also updates the runtime test Kernel version
to the LTS 6.18.18. This is because the default filesystem options
of mkfs.xfs were updated in upstream commit [3] to include new
features supported in the new Kernel 6.18.y LTS series. The commit [3]
is included in xfsprogs v6.18.
[1] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=48ccc2459039309cfbaf358febea53a86f07827c
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82394db7383d33641f3f565bd79792fb41b1741f
[3] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=54aad16b4b9b923442b4042afaba4438ca1aa868
Signed-off-by: Julien Olivain <ju.o@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 23:29:45 +01:00
Neal Frager
1d603b78c0
board/versal2/post-image.sh: remove incorrect $BINARIES_DIR
...
Remove incorrect $BINARIES_DIR reference from the symbolic link creation to
make a relative path and not an absolute path.
Signed-off-by: Neal Frager <neal.frager@amd.com >
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 22:49:31 +01:00
Thomas Richard
5af624386e
board/stmicroelectronics/stm32mp135f-dk: fix silent crash in U-Boot
...
Backport upstream patches to fix a silent crash in U-Boot on
STM32MP135F-DK.
Fixes:
799d184e89
Signed-off-by: Thomas Richard <thomas.richard@bootlin.com >
[Romain: add Fixes link]
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 22:47:33 +01:00
Giulio Benetti
1e282fbd47
package/harfbuzz: bump version to 13.1.1
...
https://github.com/harfbuzz/harfbuzz/blob/13.1.1/NEWS
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 22:39:26 +01:00
Bernd Kuhls
b2ca7b402d
package/ccache: bump version to 4.13.1
...
https://ccache.dev/releasenotes.html#_ccache_4_13_1
Updated license hash due to copyright year bump:
91a090aa02
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 22:33:01 +01:00
Yann E. MORIN
f9cdca48a5
docs/manual: use space-separated list for BR2_EXTERNAL
...
Specifying a list of br2-external trees is poorly documented, and the
only example uses a colon to separate the br2-external paths.
Adding the support for colon-separated list is the biggest mistake that
was made when introducing support for multiple br2-external [0]. Indeed,
both space and colon can be used to separate entries in the list, and it
is also possible to mix the two. However, internally, the list is stored
as a space-separated list, and all the code will split on spaces.
Besides, all other lists in Buildroot are a space-separated:
BR2_ROOTFS_DEVICE_TABLE
BR2_ROOTFS_STATIC_DEVICE_TABLE
BR2_TARGET_TZ_ZONELIST
BR2_ROOTFS_USERS_TABLES
BR2_ROOTFS_OVERLAY
BR2_ROOTFS_PRE_BUILD_SCRIPT
BR2_ROOTFS_POST_BUILD_SCRIPT
BR2_ROOTFS_POST_FAKEROOT_SCRIPT
BR2_ROOTFS_POST_IMAGE_SCRIPT
...
So, using colons is odd.
The fact that BR2_EXTERNAL is passed on the command line rather than
being a Kconfig item is not a reason enough to justify that it be
colon-separated.
Change the documentation to only mention using a space-separated list.
Of course, for backward compatibility, we keep the code as-is to accept
a colon-separated list, but we just do not advertise it.
Note that keeping the split on colons means that colons are not accepted
in pathnames of br2-external trees; in practice, this is not a new
restriction, or one that could lift as usign colons in Makefiles are
problematic anyway.
[0] in 20cd497387 core: add support for multiple br2-external trees
Reported-by: Fiona Klute (WIWA) <fiona.klute@gmx.de >
Reported-by: Brandon Maier <Brandon.Maier@collins.com >
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr >
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 22:12:18 +01:00
Yann E. MORIN
72e068001b
support/br2-external: fix remaining shellcheck errors
...
Boring changes: either do what shellcheck suggested, or comment why we
don't want to fix the code.
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 22:12:16 +01:00
Yann E. MORIN
244e4283a9
support/br2-external: remove leftover trap
...
The trap was initially introduced in c5fa9308ea (core/br2-external:
properly report unexpected errors), in 2017, to catch all unexpected
errors, back when a single file was generated, and errors emitted to
stderr.
Since commit d027cd75d0 (core: generate all br2-external files in
one go), in 2019 the single output file 'ofile' is no longer created,
as multiple output files were then introduced, while messages for
*expected errors* were redirected to a Makefile variable assignment
emitted on stdout, at which point the script just exits (in error);
expected failures only occur in do_validate().
Unexpected errors can only occur on failure to create, or write to,
output files, either '.br2-external.mk' in do_validate() or do_mk(),
or any of the kconfig fragments in do_kconfig(). Cause for failure to
create those can only be a no-space-left-on-device condition, as they
are created in a directory that was just created by the script earlier
in main(), and thus has the necessary mode; failure to create that
directory is now caught explicitly.
A trap on ERR is not called when the shell exits explicitly with a call
to 'exit', thus, only failures to create or write to output file would
be caught. In that case, we are better off not trying to write to those
files anyway: failure to create the file would already be reported by
the shell on stderr, while disk-full would not allow to store the output
anyway...
In any case, the script exits in error, which is going to be caught by
the caller, which will terminate.
So, drop the trap altogether.
As a side effect, that squelches a shellcheck error.
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr >
Signed-off-by: Romain Naour <romain.naour@smile.fr >
2026-03-13 22:12:15 +01:00
Bernd Kuhls
712e3e10cf
package/php: bump version to 8.5.4
...
https://www.php.net/ChangeLog-8.php#8.5.4
https://news-web.php.net/php.announce/486
Signed-off-by: Bernd Kuhls <bernd@kuhls.net >
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 21:58:57 +01:00
Julien Olivain
3dbb2a0aaa
arch/arm: add the Neoverse-V3AE core
...
This commit adds the Neoverse-V3AE (Automotive Enhanced) core, which
is an armv9.2a ISA. See: [1] [2].
This CPU support was added in GCC 15. See [3] [4] [5].
This CPU supports Aarch64 only at all exception levels (EL0 to EL3).
This CPU is present in NVIDIA Jetson Thor / Tegra T264 [6].
Note: at the time of this commit, the latest binutils v2.46 does not
include a Neoverse-V3AE support for its '-mcpu' option. See [7]. This is
not an issue because gcc will call the "as" assembler with the relevant
"-march=armv9.2-a+EXTENSION..." options. Binutils supports "armv9.2-a"
since upstream commit [8] (first included in 2.38), and the oldest
Binutils version in Buildroot is 2.44.
[1] https://developer.arm.com/Processors/Neoverse%20V3AE
[2] https://developer.arm.com/documentation/101595/0002/The-Neoverse-V3AE--core/Neoverse-V3AE--core-features
[3] https://gcc.gnu.org/gcc-15/changes.html#aarch64
[4] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-15.1.0#l222
[5] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=7ca2a803c4a0d8e894f0b36625a2c838c54fb4cd
[6] https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-thor/
[7] https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gas/config/tc-aarch64.c;h=cd76163488c48e45d43c35b2704d637999d51015;hb=3e93b95c3ae3f00a0283ddbab8029cbc07d96aff#l10833
[8] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=3518022233e6b757c57d3deb7723fd91214fe036
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 21:52:31 +01:00
Julien Olivain
7e75792675
arch/arm: add the Neoverse-V3 core
...
This commit adds the Neoverse-V3 core, which is an armv9.2a ISA.
See: [1] [2].
This CPU support was added in GCC 15. See [3] [4] [5].
This CPU supports Aarch64 only at all exception levels (EL0 to EL3).
Note: at the time of this commit, the latest binutils v2.46 does not
include a Neoverse-V3 support for its '-mcpu' option. See [6]. This is
not an issue because gcc will call the "as" assembler with the relevant
"-march=armv9.2-a+EXTENSION..." options. Binutils supports "armv9.2-a"
since upstream commit [7] (first included in 2.38), and the oldest
Binutils version in Buildroot is 2.44.
[1] https://developer.arm.com/Processors/Neoverse%20V3
[2] https://developer.arm.com/documentation/107734/0002/The-Neoverse--V3--core/Neoverse--V3--core-features
[3] https://gcc.gnu.org/gcc-15/changes.html#aarch64
[4] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-15.1.0#l221
[5] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=729000b90300a31ef9ed405635a0be761c5e168b
[6] https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gas/config/tc-aarch64.c;h=cd76163488c48e45d43c35b2704d637999d51015;hb=3e93b95c3ae3f00a0283ddbab8029cbc07d96aff#l10833
[7] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=3518022233e6b757c57d3deb7723fd91214fe036
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 21:52:31 +01:00
Julien Olivain
efe7aa7ca4
arch/arm: add the Neoverse-V2 core
...
This commit adds the Neoverse-V2 core, which is an armv9.0a ISA.
See: [1] [2].
This CPU support was added in GCC 13. See [3] [4] [5].
This CPU supports Aarch64 at all exception levels (EL0 to EL3).
It also supports Aarch32 only in EL0 (user-space). This means it's
technically possible to compile Aarch32 code. GCC has the support
to do so. Since Buildroot recompiles a full system (ATF, Kernel,
user-space) this support has limited value. This is why this
CPU is limited to 64bit builds only.
Note: at the time of this commit, the latest binutils v2.46 does not
include a Neoverse-V2 support for its '-mcpu' option. See [6]. This is
not an issue because gcc will call the "as" assembler with the relevant
"-march=armv9-a+EXTENSION..." options. Binutils supports "armv9-a"
since upstream commit [7] (first included in 2.38), and the oldest
Binutils version in Buildroot is 2.44.
[1] https://developer.arm.com/Processors/Neoverse%20V2
[2] https://developer.arm.com/documentation/102375/latest/
[3] https://gcc.gnu.org/gcc-13/changes.html#aarch64
[4] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-13.1.0#l184
[5] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=14d4b4fb12041dde1511262b926662929196c3fe
[6] https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gas/config/tc-aarch64.c;h=cd76163488c48e45d43c35b2704d637999d51015;hb=3e93b95c3ae3f00a0283ddbab8029cbc07d96aff#l10833
[7] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=d5007f0280d881a8add44e6a68a3f536e138244c
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 21:52:31 +01:00
Julien Olivain
99d6268223
arch/arm: add the Neoverse-V1 core
...
This commit adds the Neoverse-V1 core, which is an armv8.4a ISA.
See: [1] [2].
This CPU support was added in GCC 11. See [3] [4] [5].
This CPU supports Aarch64 at all exception levels (EL0 to EL3).
It also supports Aarch32 only in EL0 (user-space). This means it's
technically possible to compile Aarch32 code. GCC has the support
to do so. Since Buildroot recompiles a full system (ATF, Kernel,
user-space) this support has limited value. This is why this
CPU is limited to 64bit builds only.
Qemu added neoverse-v1 support in upstream commit [6], first included
in v8.1.0.
[1] https://developer.arm.com/Processors/Neoverse%20V1
[2] https://developer.arm.com/documentation/101427/0102/Functional-description/Introduction/About-the-core
[3] https://gcc.gnu.org/gcc-11/changes.html#arm-targets
[4] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-11.1.0#l141
[5] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9d56eb777552ac5ee0c281e1f6e34b6fe929b77
[6] c74138c6c0
Signed-off-by: Julien Olivain <ju.o@free.fr >
2026-03-13 21:52:31 +01:00