ARM: platform and feature deprecation
Subsystems (22)
v2 cover ARM: platform and feature deprecation
From: Arnd Bergmann <[email protected]>
Sorry for dropping the ball on v1 of this series almost two years ago. This is attempt to bring the source code to the state that we discussed back in 2024, regarding a timeline for deprecating and removing features, in particular platforms and ABIs that are basically unused and are also getting in the way of maintenance.
The earlier consensus was to remove these features in 2025 or 2026 after the corresponding LTS kernel release. I would suggest pushing these to early 2027 now, see the patch description for details on each one:
- all board files that are still not converted to DT (except for OMAP1 and S3C)
- iWMMXt FPU support
- ARMv6/ARM1136r0 (not ARMv6K/ARM1136r1/ARM1176) along with the OMAP24xx and i.MX31 SoCs using it
- Cortex-M3/M4/M7 based microcontroller support
(stm32, imxrt, lpc18xx, samv7)
- LSI Axxia platform
- OABI, OABI-compat and NWFPE are confined to StrongARM based builds and scheduled for removal once StrongARM is gone.
- DEPRECATED_PARAM_STRUCT, which was originally scheduled for removal in 2006 (!)
The ARCH_S3C64XX platform was scheduled for removal in 2024, but is still actively used and will get removed once Mark Brown stops using it. The OMAP1 platform has some remaining boardfiles and is expected to get converted to DT.
Big-endian ARMv7 CPU support is not scheduled for removal but marked as broken the same way as ARM64 has, to reduce the need for testing unused configurations. This may be removed in the future if arm64 does it as well (note: big-endian ARMv5 support is not deprecated because it is used by ixp4xx).
Regarding actually removing the code, I would suggest linux-7.4 (January 2027), removing both the board files and any drivers that have either become newly unused or were missed in a previous machine removal series, followed by removing support for then unused CPUs a release later.
Maintainers of the above features, please provide Acks or let me know if you think any of them need to hand around for longer.
Changes since v1:
- fix build failures for ARMv6 patch
- update timelines
- add a few more patches for features that were not quite as obsolete two years ago
Links to previous discussion:
https://lore.kernel.org/linux-arm-kernel/[email protected]/
https://lore.kernel.org/linux-arm-kernel/[email protected]/
https://lore.kernel.org/all/[email protected]/
Arnd Bergmann (19):
ARM: use CONFIG_AEABI by default everywhere
ARM: limit OABI support to StrongARM CPUs
ARM: rework ARM11 CPU selection logic
ARM: deprecate support for ARM1136r0
ARM: turn CONFIG_ATAGS off by default
ARM: mark CPU_ENDIAN_BE8 as deprecated
ARM: update DEPRECATED_PARAM_STRUCT removal timeline
ARM: s3c64xx: extend deprecation schedule
ARM: update FPE_NWFPE help text
ARM: mark IWMMXT as deprecated
ARM: mark ARCH_DOVE as deprecated
ARM: PXA: mark remaining board files as deprecated
ARM: orion5x: mark all board files as deprecated
ARM: mark mach-sa1100 as deprecated
ARM: mark RiscPC as deprecated
ARM: mark footbridge as deprecated
ARM: mark Cortex-M3/M4/M7 based boards as deprecated
ARM: mark axxia platform as deprecated
ARM: mark mv78xx0 support as deprecated
arch/arm/Kconfig | 80 ++++++++++++++----------- arch/arm/Kconfig.platforms | 2 +- arch/arm/configs/am200epdkit_defconfig | 3 +- arch/arm/configs/aspeed_g4_defconfig | 2 - arch/arm/configs/aspeed_g5_defconfig | 1 - arch/arm/configs/assabet_defconfig | 3 + arch/arm/configs/at91_dt_defconfig | 2 - arch/arm/configs/axm55xx_defconfig | 2 - arch/arm/configs/bcm2835_defconfig | 1 - arch/arm/configs/clps711x_defconfig | 1 - arch/arm/configs/collie_defconfig | 2 +- arch/arm/configs/davinci_all_defconfig | 1 - arch/arm/configs/dove_defconfig | 2 +- arch/arm/configs/ep93xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 2 + arch/arm/configs/gemini_defconfig | 1 - arch/arm/configs/h3600_defconfig | 3 +- arch/arm/configs/hisi_defconfig | 1 - arch/arm/configs/imx_v4_v5_defconfig | 1 - arch/arm/configs/integrator_defconfig | 2 - arch/arm/configs/ixp4xx_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 3 +- arch/arm/configs/keystone_defconfig | 1 - arch/arm/configs/lpc32xx_defconfig | 1 - arch/arm/configs/mmp2_defconfig | 1 - arch/arm/configs/moxart_defconfig | 2 - arch/arm/configs/mps2_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 2 - arch/arm/configs/multi_v5_defconfig | 10 ---- arch/arm/configs/mv78xx0_defconfig | 3 +- arch/arm/configs/mvebu_v5_defconfig | 10 ---- arch/arm/configs/mxs_defconfig | 1 - arch/arm/configs/neponset_defconfig | 3 + arch/arm/configs/netwinder_defconfig | 3 + arch/arm/configs/nhk8815_defconfig | 1 - arch/arm/configs/omap1_defconfig | 3 +- arch/arm/configs/orion5x_defconfig | 11 ---- arch/arm/configs/pxa168_defconfig | 2 - arch/arm/configs/pxa3xx_defconfig | 2 - arch/arm/configs/pxa910_defconfig | 2 - arch/arm/configs/pxa_defconfig | 5 -- arch/arm/configs/rpc_defconfig | 3 + arch/arm/configs/s3c6400_defconfig | 2 + arch/arm/configs/sama5_defconfig | 1 - arch/arm/configs/sama7_defconfig | 1 - arch/arm/configs/spear13xx_defconfig | 1 - arch/arm/configs/spitz_defconfig | 2 +- arch/arm/configs/stm32_defconfig | 3 +- arch/arm/configs/versatile_defconfig | 2 - arch/arm/configs/vt8500_v6_v7_defconfig | 1 - arch/arm/configs/wpcm450_defconfig | 2 - arch/arm/mach-at91/Kconfig | 4 +- arch/arm/mach-axxia/Kconfig | 4 +- arch/arm/mach-dove/Kconfig | 8 ++- arch/arm/mach-footbridge/Kconfig | 7 ++- arch/arm/mach-imx/Kconfig | 13 +++- arch/arm/mach-mv78xx0/Kconfig | 4 +- arch/arm/mach-omap2/Kconfig | 18 ++++-- arch/arm/mach-orion5x/Kconfig | 47 +++++++++++---- arch/arm/mach-pxa/Kconfig | 10 +++- arch/arm/mach-rpc/Kconfig | 5 +- arch/arm/mach-s3c/Kconfig.s3c64xx | 15 +++-- arch/arm/mach-sa1100/Kconfig | 5 +- arch/arm/mach-stm32/Kconfig | 14 +++-- arch/arm/mach-versatile/Kconfig | 15 +++-- arch/arm/mm/Kconfig | 29 ++++++++- 66 files changed, 227 insertions(+), 170 deletions(-)
Signature · 34 lines
2.39.5 Cc: Aaro Koskinen <[email protected]> Cc: Alexander Sverdlin <[email protected]> Cc: Alexandre Belloni <[email protected]> Cc: Alexandre Torgue <[email protected]> Cc: Andrew Lunn <[email protected]> Cc: Ard Biesheuvel <[email protected]> Cc: Claudiu Beznea <[email protected]> Cc: Daniel Mack <[email protected]> Cc: Ethan Nelson-Moore <[email protected]> Cc: Frank Li <[email protected]> Cc: Gregory Clement <[email protected]> Cc: Haojian Zhuang <[email protected]> Cc: "Jeremy J. Peper" <[email protected]> Cc: Kristoffer Ericson <[email protected]> Cc: Krzysztof Kozlowski <[email protected]> Cc: Linus Walleij <[email protected]> Cc: Mark Brown <[email protected]> Cc: Marc Zyngier <[email protected]> Cc: Mike Rapoport <[email protected]> Cc: Nicolas Ferre <[email protected]> Cc: Patrice Chotard <[email protected]> Cc: Ralph Siemsen <[email protected]> Cc: Robert Jarzmik <[email protected]> Cc: Russell King <[email protected]> Cc: Sascha Hauer <[email protected]> Cc: Sebastian Hesselbarth <[email protected]> Cc: Stefan Agner <[email protected]> Cc: Stefan Wiehler <[email protected]> Cc: Tony Lindgren <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Cc: Will Deacon <[email protected]> Cc: [email protected]
PATCH v2 1/19 ARM: use CONFIG_AEABI by default everywhere
From: Arnd Bergmann <[email protected]>
On ARMv4 and ARMv5, the default is still to build for OABI, with CONFIG_AEABI disabled, even though distros and toolchains no longer support OABI as a target.
Change the default to EABI for all architecture levels and change the defconfig entries as follows:
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig (at91_dt, collie, ep93xx, gemini, h3600, imx_v4_v5, integrator, jornada, moxart, multi_v4t, omap1) were likely not usable with either OABI or EABI and now use EABI instead implicitly, making it more likely that they could work.
--- arch/arm/Kconfig | 15 ++++++--------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/assabet_defconfig | 1 + arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/bcm2835_defconfig | 1 - arch/arm/configs/clps711x_defconfig | 1 - arch/arm/configs/collie_defconfig | 1 - arch/arm/configs/davinci_all_defconfig | 1 - arch/arm/configs/dove_defconfig | 1 - arch/arm/configs/ep93xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 1 + arch/arm/configs/gemini_defconfig | 1 - arch/arm/configs/h3600_defconfig | 1 - arch/arm/configs/hisi_defconfig | 1 - arch/arm/configs/imx_v4_v5_defconfig | 1 - arch/arm/configs/integrator_defconfig | 1 - arch/arm/configs/ixp4xx_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 1 - arch/arm/configs/keystone_defconfig | 1 - arch/arm/configs/lpc32xx_defconfig | 1 - arch/arm/configs/mmp2_defconfig | 1 - arch/arm/configs/moxart_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 1 - arch/arm/configs/multi_v5_defconfig | 1 - arch/arm/configs/mv78xx0_defconfig | 2 -- arch/arm/configs/mvebu_v5_defconfig | 1 - arch/arm/configs/mxs_defconfig | 1 - arch/arm/configs/neponset_defconfig | 1 + arch/arm/configs/netwinder_defconfig | 1 + arch/arm/configs/nhk8815_defconfig | 1 - arch/arm/configs/omap1_defconfig | 2 -- arch/arm/configs/orion5x_defconfig | 2 -- arch/arm/configs/pxa168_defconfig | 2 -- arch/arm/configs/pxa3xx_defconfig | 2 -- arch/arm/configs/pxa910_defconfig | 2 -- arch/arm/configs/pxa_defconfig | 1 - arch/arm/configs/rpc_defconfig | 1 + arch/arm/configs/spear13xx_defconfig | 1 - arch/arm/configs/spitz_defconfig | 1 - arch/arm/configs/versatile_defconfig | 1 - arch/arm/configs/vt8500_v6_v7_defconfig | 1 - arch/arm/configs/wpcm450_defconfig | 1 - 44 files changed, 11 insertions(+), 53 deletions(-)
arch/arm/Kconfig +6 -9
@@ -1153,17 +1153,14 @@ config ARM_PATCH_IDIV config AEABI bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \ !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG - default CPU_V7 || CPU_V7M || CPU_V6 || CPU_V6K || CC_IS_CLANG + default y help - This option allows for the kernel to be compiled using the latest - ARM ABI (aka EABI). This is only useful if you are using a user - space environment that is also compiled with EABI. + The Arm EABI is the default ABI on all modern Linux + distributions, replacing the obsolete and "OABI" that was + commonly used on ARMv4 distributions before ca. 2013. - Since there are major incompatibilities between the legacy ABI and - EABI, especially with regard to structure member alignment, this - option also changes the kernel syscall calling convention to - disambiguate both ABIs and allow for backward compatibility support - (selected with CONFIG_OABI_COMPAT). + Everyone should enable this, as support for OABI user space + was dropped in gcc-4.8 and most distributions after ca. 2013. config OABI_COMPAT bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
arch/arm/configs/am200epdkit_defconfig +0 -1
@@ -7,7 +7,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y -CONFIG_AEABI=y # CONFIG_OABI_COMPAT is not set CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=y
arch/arm/configs/aspeed_g4_defconfig +0 -1
@@ -22,7 +22,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_ASPEED=y CONFIG_MACH_ASPEED_G4=y CONFIG_VMSPLIT_2G=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_JUMP_LABEL=y
arch/arm/configs/assabet_defconfig +1 -0
@@ -5,6 +5,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y +# CONFIG_AEABI is not set CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram" CONFIG_FPE_NWFPE=y CONFIG_PM=y
arch/arm/configs/at91_dt_defconfig +0 -1
@@ -18,7 +18,6 @@ CONFIG_SOC_AT91SAM9=y CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y
arch/arm/configs/axm55xx_defconfig +0 -1
@@ -38,7 +38,6 @@ CONFIG_PCIE_AXXIA=y CONFIG_SMP=y CONFIG_NR_CPUS=16 CONFIG_HOTPLUG_CPU=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y
arch/arm/configs/bcm2835_defconfig +0 -1
@@ -25,7 +25,6 @@ CONFIG_CRASH_DUMP=y CONFIG_ARCH_MULTI_V6=y CONFIG_ARCH_BCM=y CONFIG_ARCH_BCM2835=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_KEXEC=y CONFIG_CPU_FREQ=y
arch/arm/configs/clps711x_defconfig +0 -1
@@ -6,7 +6,6 @@ CONFIG_RD_LZMA=y CONFIG_EXPERT=y CONFIG_JUMP_LABEL=y CONFIG_PARTITION_ADVANCED=y -CONFIG_AEABI=y # CONFIG_COREDUMP is not set CONFIG_SLUB_TINY=y CONFIG_NET=y
arch/arm/configs/collie_defconfig +0 -1
@@ -10,7 +10,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_COLLIE=y CONFIG_CMDLINE="noinitrd root=/dev/mtdblock2 rootfstype=jffs2 fbcon=rotate:1" -CONFIG_FPE_NWFPE=y CONFIG_PM=y # CONFIG_SWAP is not set CONFIG_SLUB_TINY=y
arch/arm/configs/davinci_all_defconfig +0 -1
@@ -17,7 +17,6 @@ CONFIG_ARCH_DAVINCI=y CONFIG_ARCH_DAVINCI_DA850=y CONFIG_DAVINCI_MUX_DEBUG=y CONFIG_DAVINCI_MUX_WARNINGS=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/dove_defconfig +0 -1
@@ -7,7 +7,6 @@ CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_DOVE=y CONFIG_MACH_CM_A510=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/ep93xx_defconfig +0 -1
@@ -18,7 +18,6 @@ CONFIG_MACH_EDB9315=y CONFIG_MACH_EDB9315A=y CONFIG_MACH_TS72XX=y CONFIG_MACH_VISION_EP9307=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyAM0,115200 root=/dev/nfs ip=bootp" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/footbridge_defconfig +1 -0
@@ -11,6 +11,7 @@ CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=y
arch/arm/configs/gemini_defconfig +0 -1
@@ -11,7 +11,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_GEMINI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_CMDLINE="console=ttyS0,115200n8" CONFIG_PM=y
arch/arm/configs/h3600_defconfig +0 -1
@@ -9,7 +9,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_H3600=y # CONFIG_CPU_FREQ_STAT is not set -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_UNIX=y
arch/arm/configs/hisi_defconfig +0 -1
@@ -10,7 +10,6 @@ CONFIG_ARCH_HIP04=y CONFIG_ARCH_HIX5HD2=y CONFIG_SMP=y CONFIG_NR_CPUS=16 -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/imx_v4_v5_defconfig +0 -1
@@ -15,7 +15,6 @@ CONFIG_ARCH_MXC=y CONFIG_SOC_IMX1=y CONFIG_SOC_IMX25=y CONFIG_SOC_IMX27=y -CONFIG_AEABI=y CONFIG_PM_DEBUG=y CONFIG_KPROBES=y CONFIG_MODULES=y
arch/arm/configs/integrator_defconfig +0 -1
@@ -13,7 +13,6 @@ CONFIG_ARCH_INTEGRATOR=y CONFIG_ARCH_INTEGRATOR_AP=y CONFIG_INTEGRATOR_IMPD1=y CONFIG_ARCH_INTEGRATOR_CP=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyAM0,38400n8 root=/dev/nfs ip=bootp" CONFIG_CPU_FREQ=y
arch/arm/configs/ixp4xx_defconfig +0 -1
@@ -9,7 +9,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_IXP4XX=y CONFIG_CPU_BIG_ENDIAN=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyS0,115200" CONFIG_STRICT_KERNEL_RWX=y CONFIG_STRICT_MODULE_RWX=y
arch/arm/configs/jornada720_defconfig +0 -1
@@ -5,7 +5,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_JORNADA720=y CONFIG_SA1100_JORNADA720_SSP=y -CONFIG_FPE_NWFPE=y CONFIG_PM=y CONFIG_MODULES=y CONFIG_NET=y
arch/arm/configs/keystone_defconfig +0 -1
@@ -22,7 +22,6 @@ CONFIG_PCI_KEYSTONE=y CONFIG_SMP=y CONFIG_HOTPLUG_CPU=y CONFIG_ARM_PSCI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_VFP=y CONFIG_NEON=y
arch/arm/configs/lpc32xx_defconfig +0 -1
@@ -10,7 +10,6 @@ CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_LPC32XX=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CMDLINE="console=ttyS0,115200n81 root=/dev/ram0"
arch/arm/configs/mmp2_defconfig +0 -1
@@ -4,7 +4,6 @@ CONFIG_PREEMPT=y CONFIG_LOG_BUF_SHIFT=14 # CONFIG_BLK_DEV_BSG is not set CONFIG_ARCH_MMP=y -CONFIG_AEABI=y CONFIG_MACH_MMP2_DT=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS2,38400 mem=128M user_debug=255 earlyprintk" CONFIG_VFP=y
arch/arm/configs/moxart_defconfig +0 -1
@@ -16,7 +16,6 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MOXART=y CONFIG_MACH_UC7112LX=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y # CONFIG_SWAP is not set
arch/arm/configs/multi_v4t_defconfig +0 -1
@@ -17,7 +17,6 @@ CONFIG_INTEGRATOR_IMPD1=y CONFIG_INTEGRATOR_CM720T=y CONFIG_INTEGRATOR_CM920T=y CONFIG_INTEGRATOR_CM922T_XA10=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CPU_IDLE=y CONFIG_ARM_CPUIDLE=y
arch/arm/configs/multi_v5_defconfig +0 -1
@@ -36,7 +36,6 @@ CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/mv78xx0_defconfig +0 -2
@@ -11,9 +11,7 @@ CONFIG_ARCH_MULTI_V5=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MV78XX0=y CONFIG_MACH_TERASTATION_WXL=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=y
arch/arm/configs/mvebu_v5_defconfig +0 -1
@@ -22,7 +22,6 @@ CONFIG_MACH_MV2120=y CONFIG_MACH_D2NET_DT=y CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/mxs_defconfig +0 -1
@@ -17,7 +17,6 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_PERF_EVENTS=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MXS=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/neponset_defconfig +1 -0
@@ -11,6 +11,7 @@ CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y CONFIG_CMDLINE="console=ttySA0,38400n8 cpufreq=221200 rw root=/dev/mtdblock2 mtdparts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) mem=32M noinitrd initrd=0xc0800000,3M" CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_PM=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/netwinder_defconfig +1 -0
@@ -4,6 +4,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_DEPRECATED_PARAM_STRUCT=y CONFIG_CMDLINE="root=0x801" CONFIG_FPE_NWFPE=y
arch/arm/configs/nhk8815_defconfig +0 -1
@@ -12,7 +12,6 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_NOMADIK=y CONFIG_MACH_NOMADIK_8815NHK=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_SWAP is not set
arch/arm/configs/omap1_defconfig +0 -2
@@ -28,9 +28,7 @@ CONFIG_MACH_OMAP_PALMTE=y CONFIG_MACH_SX1=y CONFIG_MACH_NOKIA770=y CONFIG_MACH_AMS_DELTA=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=1f03 rootfstype=jffs2" -CONFIG_FPE_NWFPE=y # CONFIG_SUSPEND is not set CONFIG_PM=y CONFIG_MODULES=y
arch/arm/configs/orion5x_defconfig +0 -2
@@ -20,10 +20,8 @@ CONFIG_MACH_TS409=y CONFIG_MACH_TS78XX=y CONFIG_MACH_MV2120=y CONFIG_MACH_NET2BIG=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=y
arch/arm/configs/pxa168_defconfig +0 -2
@@ -3,11 +3,9 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ_IDLE=y CONFIG_HIGH_RES_TIMERS=y CONFIG_PREEMPT=y -CONFIG_AEABI=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_ARCH_MMP=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.2.100:/nfsroot/ ip=192.168.2.101:192.168.2.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=128M" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y
arch/arm/configs/pxa3xx_defconfig +0 -2
@@ -7,9 +7,7 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_MACH_PXA3XX_DT=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=64M debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_PACKET=y
arch/arm/configs/pxa910_defconfig +0 -2
@@ -10,8 +10,6 @@ CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_BLK_DEV_BSG is not set -CONFIG_AEABI=y -CONFIG_FPE_NWFPE=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=y
arch/arm/configs/pxa_defconfig +0 -1
@@ -20,7 +20,6 @@ CONFIG_ARCH_GUMSTIX=y CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y -CONFIG_AEABI=y CONFIG_ARCH_FORCE_MAX_ORDER=8 CONFIG_CMDLINE="root=/dev/ram0 ro" CONFIG_CPU_FREQ=y
arch/arm/configs/rpc_defconfig +1 -0
@@ -7,6 +7,7 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_RPC=y CONFIG_CPU_SA110=y CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=y
arch/arm/configs/spear13xx_defconfig +0 -1
@@ -9,7 +9,6 @@ CONFIG_MACH_SPEAR1340=y CONFIG_SMP=y # CONFIG_SMP_ON_UP is not set # CONFIG_ARM_CPU_TOPOLOGY is not set -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=y
arch/arm/configs/spitz_defconfig +0 -1
@@ -11,7 +11,6 @@ CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/mtdblock2 rootfstype=jffs2 debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y
arch/arm/configs/versatile_defconfig +0 -1
@@ -6,7 +6,6 @@ CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_CMDLINE="root=1f03 mem=32M" CONFIG_FPE_NWFPE=y
arch/arm/configs/vt8500_v6_v7_defconfig +0 -1
@@ -8,7 +8,6 @@ CONFIG_ARM_ERRATA_720789=y CONFIG_ARM_ERRATA_754322=y CONFIG_ARM_ERRATA_775420=y CONFIG_HAVE_ARM_ARCH_TIMER=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y CONFIG_ARM_APPENDED_DTB=y
arch/arm/configs/wpcm450_defconfig +0 -1
@@ -13,7 +13,6 @@ CONFIG_PROFILING=y CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_CPU_DCACHE_WRITETHROUGH=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y
Signature · 1 line
2.39.5
PATCH v2 2/19 ARM: limit OABI support to StrongARM CPUs
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
As discussed on the mailing lists, there is no way to build OABI userspace binaries any more since gcc-4.8, and now support is also getting dropped in binutils, which will make it impossible to build pure OABI kernels at some point in the future.
I found no evidence of anyone still sing OABI userspace on embedded systems that keep getting kernel updates, but there are a few desktop-class machines that date back to the 1990s using Intel StrongARM processors that were supported by old versions of Debian, Red Hat or the official Corel Netwinder distribution.
Add a much stricter Kconfig dependency for both native OABI and OABI_COMPAT enabled kernels, only allowing either of them to be selected when building a kernel that targets a StrongARM based machine.
--- arch/arm/Kconfig | 14 +++++++------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 2 +- arch/arm/configs/neponset_defconfig | 2 +- arch/arm/configs/versatile_defconfig | 1 - 6 files changed, 9 insertions(+), 12 deletions(-)
arch/arm/Kconfig +7 -7
@@ -1151,8 +1151,7 @@ config ARM_PATCH_IDIV code to do integer division. config AEABI - bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \ - !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG + bool "Use the ARM EABI to compile the kernel" if CPU_SA110 || CPU_SA1100 default y help The Arm EABI is the default ABI on all modern Linux
@@ -1162,9 +1161,13 @@ config AEABI Everyone should enable this, as support for OABI user space was dropped in gcc-4.8 and most distributions after ca. 2013. + Support for OABI mode will be removed from the kernel + once Intel StrongARM CPUs are phased out. + config OABI_COMPAT bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)" depends on AEABI && !THUMB2_KERNEL + depends on CPU_SA110 || CPU_SA1100 help This option preserves the old syscall interface along with the new (ARM EABI) one. It also provides a compatibility layer to
@@ -1177,11 +1180,8 @@ config OABI_COMPAT selected, since there is no way yet to sensibly distinguish between calling conventions during filtering. - If you know you'll be using only pure EABI user space then you - can say N here. If this option is not selected and you attempt - to execute a legacy ABI binary then the result will be - UNPREDICTABLE (in fact it can be predicted that it won't work - at all). If in doubt say N. + Support for OABI_COMPAT will be removed from the kernel + once Intel StrongARM CPUs are phased out. config ARCH_SELECT_MEMORY_MODEL def_bool y
arch/arm/configs/am200epdkit_defconfig +0 -1
@@ -7,7 +7,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y -# CONFIG_OABI_COMPAT is not set CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/axm55xx_defconfig +0 -1
@@ -38,7 +38,6 @@ CONFIG_PCIE_AXXIA=y CONFIG_SMP=y CONFIG_NR_CPUS=16 CONFIG_HOTPLUG_CPU=y -CONFIG_OABI_COMPAT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y
arch/arm/configs/footbridge_defconfig +1 -1
@@ -9,9 +9,9 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y -# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=y
arch/arm/configs/neponset_defconfig +1 -1
@@ -6,12 +6,12 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y CONFIG_ASSABET_NEPONSET=y +# CONFIG_AEABI is not set CONFIG_ZBOOT_ROM_TEXT=0x80000 CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y CONFIG_CMDLINE="console=ttySA0,38400n8 cpufreq=221200 rw root=/dev/mtdblock2 mtdparts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) mem=32M noinitrd initrd=0xc0800000,3M" CONFIG_FPE_NWFPE=y -# CONFIG_AEABI is not set CONFIG_PM=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/versatile_defconfig +0 -1
@@ -6,7 +6,6 @@ CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_VERSATILE=y -CONFIG_OABI_COMPAT=y CONFIG_CMDLINE="root=1f03 mem=32M" CONFIG_FPE_NWFPE=y CONFIG_VFP=y
Signature · 1 line
2.39.5
PATCH v2 3/19 ARM: rework ARM11 CPU selection logic
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Support for SMP on ARM1136r0 has been broken for a while, and nobody is working on fixing it. I had a plan to change ARMv6 support to no longer coexist in a common kernel with ARMv7 CPUs but instead ARMv5 and below. This would have addressed the problem, but after a recent mailing list discussion, we concluded that an easier approach is to just forbid ARM1136r0 CPU support on SMP-enabled kernels.
This mainly affects users of the Nokia N800/N810 tablets using an OMAP2420 SoC, which is the only commercial product with an ARM1136r0 that is still supported by the kernel.
The other machines that are still in the same hardware catogory are:
- TI OMAP2420 H4 reference board
- TI OMAP2430 SDP software development platform
- Freescale/NXP i.MX31 Lite Development Kit
- Buglabs i.MX31 Bug 1.x prototype
- Arm Integrator/AP with CM1136JF-S core module
To my knowledge, none of these have any actual users aside from reference boards being used more easily test the platforms.
There are also a few ARM1136r1 machines, which implement the ARMv6K SMP support (barriers, atomics and TLS):
- Eukrea CPUIMX35 reference platform
- Freescale/NXP i.MX35 Product Development Kit
- ARM Integrator/CP/IM-LT3 with ARM1136J Core Tile
- ARM Realview/EB with ARM1136J Core Tile
Again, these are mainly reference implementations rather than actual products, but since they support ARMv6K, they should continue to work correctly in SMP-enabled kernels. For the ARM Core Tile, I have not found a datasheet but instead use the revision based on what the respective virtual models report.
All the other ARMv6 platforms use an ARM1176 with ARMv6K, VMSAv7 and Trustzone support.
To avoid the broken configuration, annotate the ARM1136 based machines with specific CPU_ARM1136R0 or CPU_ARM1136R2 symbols in Kconfig and make the r0 variants depend on !SMP.
--- arch/arm/Kconfig.platforms | 2 +- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-omap2/Kconfig | 3 ++- arch/arm/mach-versatile/Kconfig | 10 +++++----- arch/arm/mm/Kconfig | 24 +++++++++++++++++++++++- 5 files changed, 34 insertions(+), 9 deletions(-)
arch/arm/Kconfig.platforms +1 -1
@@ -33,7 +33,7 @@ config ARCH_MULTI_V4_V5 config ARCH_MULTI_V6 bool "ARMv6 based platforms (ARM11)" select ARCH_MULTI_V6_V7 - select CPU_V6K + select CPU_ARM1176 config ARCH_MULTI_V7 bool "ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)"
arch/arm/mach-imx/Kconfig +3 -1
@@ -41,13 +41,15 @@ comment "ARM1136 platforms" config SOC_IMX31 bool "i.MX31 support" - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor config SOC_IMX35 bool "i.MX35 support" + select CPU_ARM1136R1 select MXC_AVIC help This enables support for Freescale i.MX35 processor
arch/arm/mach-omap2/Kconfig +2 -1
@@ -8,8 +8,9 @@ config OMAP_HWMOD config ARCH_OMAP2 bool "TI OMAP2" depends on ARCH_MULTI_V6 + depends on !SMP select ARCH_OMAP2PLUS - select CPU_V6 + select CPU_ARM1136R0 select OMAP_HWMOD select SOC_HAS_OMAP2_SDRC
arch/arm/mach-versatile/Kconfig +5 -5
@@ -113,7 +113,8 @@ config INTEGRATOR_CM1136JFS bool "Integrator/CM1136JF-S core module" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"
@@ -135,7 +136,7 @@ config INTEGRATOR_CTB36 bool "Integrator/CTB36 (ARM1136JF-S) core tile" depends on ARCH_INTEGRATOR_CP depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 config ARCH_CINTEGRATOR depends on ARCH_INTEGRATOR_CP
@@ -182,7 +183,7 @@ config MACH_REALVIEW_EB config REALVIEW_EB_ARM1136 bool "Support ARM1136J(F)-S Tile" depends on MACH_REALVIEW_EB && ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 help Enable support for the ARM1136 tile fitted to the Realview(R) Emulation Baseboard platform.
@@ -201,11 +202,10 @@ config REALVIEW_EB_A9MP Enable support for the Cortex-A9MPCore tile fitted to the Realview(R) Emulation Baseboard platform. -# ARMv6 CPU without K extensions, but does have the new exclusive ops config MACH_REALVIEW_PB1176 bool "Support RealView(R) Platform Baseboard for ARM1176JZF-S" depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1176 select HAVE_TCM help Include support for the ARM(R) RealView(R) Platform Baseboard for
arch/arm/mm/Kconfig +23 -1
@@ -376,6 +376,7 @@ config CPU_PJ4B # ARMv6 config CPU_V6 bool + depends on !SMP select CPU_32v6 select CPU_ABRT_EV6 select CPU_CACHE_V6
@@ -386,7 +387,6 @@ config CPU_V6 select CPU_PABRT_V6 select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU - select SMP_ON_UP if SMP # ARMv6k config CPU_V6K
@@ -403,6 +403,28 @@ config CPU_V6K select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU +config CPU_ARM1136R0 + bool + select CPU_V6 + depends on !SMP + help + These early revisions of ARM1136 lack support for the + ARMv6k extensions for multiprocessing. + +config CPU_ARM1136R1 + bool + select CPU_V6K + help + Later revisions of ARM1136 add ARMv6k (atomics, barriers + and TLS register) in addition to the features from r0. + +config CPU_ARM1176 + bool + select CPU_V6K + help + ARM1176 implements ARMv6k, VMSAv7 and Trustzone in + addition to the ARMv6 baseline. + # ARMv7 and ARMv8 architectures config CPU_V7 bool
Signature · 1 line
2.39.5
PATCH v2 4/19 ARM: deprecate support for ARM1136r0
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
This CPU revision remains a special case as it is now incompatible with CONFIG_SMP. Only the Nokia N8x0 is used in practice, and even that one is fairly rare these days, so let's plan to remove all of them after the 2026 LTS kernel release.
--- arch/arm/mach-imx/Kconfig | 5 ++++- arch/arm/mach-omap2/Kconfig | 15 ++++++++++++--- arch/arm/mach-versatile/Kconfig | 5 ++++- arch/arm/mm/Kconfig | 2 ++ 4 files changed, 22 insertions(+), 5 deletions(-)
arch/arm/mach-imx/Kconfig +4 -1
@@ -40,13 +40,16 @@ if ARCH_MULTI_V6 comment "ARM1136 platforms" config SOC_IMX31 - bool "i.MX31 support" + bool "i.MX31 support (DEPRECATED)" depends on !SMP select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. + config SOC_IMX35 bool "i.MX35 support" select CPU_ARM1136R1
arch/arm/mach-omap2/Kconfig +12 -3
@@ -207,18 +207,24 @@ comment "OMAP Core Type" depends on ARCH_OMAP2 config SOC_OMAP2420 - bool "OMAP2420 support" + bool "OMAP2420 support (DEPRECATED)" depends on ARCH_OMAP2 default y select OMAP_DM_SYSTIMER select OMAP_DM_TIMER select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP2430 - bool "OMAP2430 support" + bool "OMAP2430 support (DEPRECATED)" depends on ARCH_OMAP2 default y select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP3430 bool "OMAP3430 support"
@@ -249,11 +255,14 @@ config MACH_NOKIA_N810_WIMAX bool config MACH_NOKIA_N8X0 - bool "Nokia N800/N810" + bool "Nokia N800/N810 (DEPRECATED)" depends on SOC_OMAP2420 default y select MACH_NOKIA_N810 select MACH_NOKIA_N810_WIMAX + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. endmenu
arch/arm/mach-versatile/Kconfig +4 -1
@@ -110,11 +110,14 @@ config INTEGRATOR_CM1026EJS select CPU_ARM1026 config INTEGRATOR_CM1136JFS - bool "Integrator/CM1136JF-S core module" + bool "Integrator/CM1136JF-S core module (DEPRECATED)" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 depends on !SMP select CPU_ARM1136R0 + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"
arch/arm/mm/Kconfig +2 -0
@@ -410,6 +410,8 @@ config CPU_ARM1136R0 help These early revisions of ARM1136 lack support for the ARMv6k extensions for multiprocessing. + Support for this revision is scheduled for removal + from the kernel in early 2027. config CPU_ARM1136R1 bool
Signature · 1 line
2.39.5
PATCH v2 5/19 ARM: turn CONFIG_ATAGS off by default
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Only a very small number of machines remain that rely on traditional board files with the ATAGS boot data instead of devicetree, and we have not accepted new ones for a decade.
Most of the remaining ones are on their way out of the kernel, but the Kconfig option that controls ATAGS is still enabled by default.
To reflect the actual status of ATAGS support and alert the remaining users of upstream and out-of-tree platforms with this, chanyge it to being default-disabled and add a dependency on CONFIG_EXPERT.
The board specific defconfig files that rely on ATAGS are changed to turn on both EXPERT and ATAGS if they were not doing thath already, and the ones that explicitly turned it off before no longer need to.
--- arch/arm/Kconfig | 13 ++++++++----- arch/arm/configs/am200epdkit_defconfig | 1 + arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/aspeed_g5_defconfig | 1 - arch/arm/configs/assabet_defconfig | 2 ++ arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/collie_defconfig | 1 + arch/arm/configs/dove_defconfig | 1 + arch/arm/configs/footbridge_defconfig | 1 + arch/arm/configs/h3600_defconfig | 2 ++ arch/arm/configs/integrator_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 2 ++ arch/arm/configs/moxart_defconfig | 1 - arch/arm/configs/mps2_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 1 - arch/arm/configs/mv78xx0_defconfig | 1 + arch/arm/configs/neponset_defconfig | 2 ++ arch/arm/configs/netwinder_defconfig | 2 ++ arch/arm/configs/omap1_defconfig | 1 + arch/arm/configs/rpc_defconfig | 2 ++ arch/arm/configs/s3c6400_defconfig | 2 ++ arch/arm/configs/sama5_defconfig | 1 - arch/arm/configs/sama7_defconfig | 1 - arch/arm/configs/spitz_defconfig | 1 + arch/arm/configs/stm32_defconfig | 3 ++- arch/arm/configs/wpcm450_defconfig | 1 - 26 files changed, 31 insertions(+), 16 deletions(-)
arch/arm/Kconfig +8 -5
@@ -1390,12 +1390,15 @@ config ARCH_WANT_FLAT_DTB_INSTALL config ATAGS bool "Support for the traditional ATAGS boot data passing" - default y + depends on EXPERT help - This is the traditional way of passing data to the kernel at boot - time. If you are solely relying on the flattened device tree (or - the ARM_ATAG_DTB_COMPAT option) then you may unselect this option - to remove ATAGS support from your kernel binary. + This is the traditional way of passing data to the kernel at + boot but is now only used by a few of the oldest ARMv4 and + ARMv5 machines. Users that still rely on ATAGS should plan + on migrating to devicetree based booting. + + Support for ATAGS will be removed when the last machine using + it is either converted to DT or removed. config DEPRECATED_PARAM_STRUCT bool "Provide old way to pass kernel parameters"
arch/arm/configs/am200epdkit_defconfig +1 -0
@@ -7,6 +7,7 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/aspeed_g4_defconfig +0 -1
@@ -23,7 +23,6 @@ CONFIG_ARCH_ASPEED=y CONFIG_MACH_ASPEED_G4=y CONFIG_VMSPLIT_2G=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_JUMP_LABEL=y CONFIG_STRICT_KERNEL_RWX=y # CONFIG_BLK_DEBUG_FS is not set
arch/arm/configs/aspeed_g5_defconfig +0 -1
@@ -29,7 +29,6 @@ CONFIG_VMSPLIT_2G=y CONFIG_NR_CPUS=2 CONFIG_HIGHMEM=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_VFP=y CONFIG_NEON=y CONFIG_KERNEL_MODE_NEON=y
arch/arm/configs/assabet_defconfig +2 -0
@@ -1,11 +1,13 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram" CONFIG_FPE_NWFPE=y CONFIG_PM=y
arch/arm/configs/at91_dt_defconfig +0 -1
@@ -19,7 +19,6 @@ CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw"
arch/arm/configs/collie_defconfig +1 -0
@@ -9,6 +9,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_COLLIE=y +CONFIG_ATAGS=y CONFIG_CMDLINE="noinitrd root=/dev/mtdblock2 rootfstype=jffs2 fbcon=rotate:1" CONFIG_PM=y # CONFIG_SWAP is not set
arch/arm/configs/dove_defconfig +1 -0
@@ -8,6 +8,7 @@ CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_DOVE=y CONFIG_MACH_CM_A510=y CONFIG_HIGHMEM=y +CONFIG_ATAGS=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=y
arch/arm/configs/footbridge_defconfig +1 -0
@@ -10,6 +10,7 @@ CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y CONFIG_MODULES=y
arch/arm/configs/h3600_defconfig +2 -0
@@ -4,11 +4,13 @@ CONFIG_HIGH_RES_TIMERS=y CONFIG_PREEMPT=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_H3600=y # CONFIG_CPU_FREQ_STAT is not set +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_UNIX=y
arch/arm/configs/integrator_defconfig +0 -1
@@ -13,7 +13,6 @@ CONFIG_ARCH_INTEGRATOR=y CONFIG_ARCH_INTEGRATOR_AP=y CONFIG_INTEGRATOR_IMPD1=y CONFIG_ARCH_INTEGRATOR_CP=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyAM0,38400n8 root=/dev/nfs ip=bootp" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y
arch/arm/configs/jornada720_defconfig +2 -0
@@ -1,11 +1,13 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_JORNADA720=y CONFIG_SA1100_JORNADA720_SSP=y CONFIG_PM=y +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_PACKET=y
arch/arm/configs/moxart_defconfig +0 -1
@@ -16,7 +16,6 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MOXART=y CONFIG_MACH_UC7112LX=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y # CONFIG_SWAP is not set # CONFIG_COMPAT_BRK is not set
arch/arm/configs/mps2_defconfig +0 -1
@@ -16,7 +16,6 @@ CONFIG_ARCH_MPS2=y CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x21000000 CONFIG_DRAM_SIZE=0x1000000 -# CONFIG_ATAGS is not set # CONFIG_SUSPEND is not set # CONFIG_BLOCK is not set CONFIG_BINFMT_FLAT=y
arch/arm/configs/multi_v4t_defconfig +0 -1
@@ -17,7 +17,6 @@ CONFIG_INTEGRATOR_IMPD1=y CONFIG_INTEGRATOR_CM720T=y CONFIG_INTEGRATOR_CM920T=y CONFIG_INTEGRATOR_CM922T_XA10=y -# CONFIG_ATAGS is not set CONFIG_CPU_IDLE=y CONFIG_ARM_CPUIDLE=y CONFIG_ARM_CLPS711X_CPUIDLE=y
arch/arm/configs/mv78xx0_defconfig +1 -0
@@ -12,6 +12,7 @@ CONFIG_ARCH_MULTI_V5=y CONFIG_ARCH_MV78XX0=y CONFIG_MACH_TERASTATION_WXL=y CONFIG_HIGHMEM=y +CONFIG_ATAGS=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=y
arch/arm/configs/neponset_defconfig +2 -0
@@ -1,12 +1,14 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y CONFIG_ASSABET_NEPONSET=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_ZBOOT_ROM_TEXT=0x80000 CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y
arch/arm/configs/netwinder_defconfig +2 -0
@@ -1,10 +1,12 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_NETWINDER=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_DEPRECATED_PARAM_STRUCT=y CONFIG_CMDLINE="root=0x801" CONFIG_FPE_NWFPE=y
arch/arm/configs/omap1_defconfig +1 -0
@@ -28,6 +28,7 @@ CONFIG_MACH_OMAP_PALMTE=y CONFIG_MACH_SX1=y CONFIG_MACH_NOKIA770=y CONFIG_MACH_AMS_DELTA=y +CONFIG_ATAGS=y CONFIG_CMDLINE="root=1f03 rootfstype=jffs2" # CONFIG_SUSPEND is not set CONFIG_PM=y
arch/arm/configs/rpc_defconfig +2 -0
@@ -2,12 +2,14 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_RPC=y CONFIG_CPU_SA110=y CONFIG_FPE_NWFPE=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=y
arch/arm/configs/s3c6400_defconfig +2 -0
@@ -2,8 +2,10 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_KALLSYMS_ALL=y CONFIG_ARCH_MULTI_V6=y # CONFIG_ARCH_MULTI_V7 is not set +CONFIG_EXPERT=y CONFIG_ARCH_S3C64XX=y CONFIG_MACH_WLF_CRAGG_6410=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttySAC0,115200 root=/dev/ram init=/linuxrc initrd=0x51000000,6M ramdisk_size=6144" CONFIG_VFP=y CONFIG_MODULES=y
arch/arm/configs/sama5_defconfig +0 -1
@@ -13,7 +13,6 @@ CONFIG_SOC_SAMA5D3=y CONFIG_SOC_SAMA5D4=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw" CONFIG_VFP=y CONFIG_NEON=y
arch/arm/configs/sama7_defconfig +0 -1
@@ -20,7 +20,6 @@ CONFIG_ATMEL_CLOCKSOURCE_TCB=y # CONFIG_CPU_SW_DOMAIN_PAN is not set CONFIG_ARCH_FORCE_MAX_ORDER=14 CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyS0,115200 earlyprintk ignore_loglevel" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE=y
arch/arm/configs/spitz_defconfig +1 -0
@@ -10,6 +10,7 @@ CONFIG_ARCH_PXA=y CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/mtdblock2 rootfstype=jffs2 debug" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y
arch/arm/configs/stm32_defconfig +2 -1
@@ -20,7 +20,8 @@ CONFIG_ARCH_STM32=y CONFIG_CPU_V7M_NUM_IRQ=240 CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x90000000 -# CONFIG_ATAGS is not set +CONFIG_FLASH_MEM_BASE=0x08000000 +CONFIG_FLASH_SIZE=0x00200000 CONFIG_XIP_KERNEL=y CONFIG_XIP_PHYS_ADDR=0x08008000 # CONFIG_SUSPEND is not set
arch/arm/configs/wpcm450_defconfig +0 -1
@@ -14,7 +14,6 @@ CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_CPU_DCACHE_WRITETHROUGH=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y CONFIG_CPU_IDLE=y CONFIG_KPROBES=y
Signature · 1 line
2.39.5
PATCH v2 6/19 ARM: mark CPU_ENDIAN_BE8 as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Following the deprecation of big-endian ARMv8 mode in arch/arm64 in commit 1cf89b6bf660 ("arm64: Kconfig: Make CPU_BIG_ENDIAN depend on BROKEN"), this does the same for ARMv7 (and v6), leaving the code around but disabled by default: There are no known products that make use of this mode any more, and it only hangs around for testing that it still works.
At the moment, there are no known bugs with big-endian ARMv7 mode, but it does break occasionally and require someone to fix it. By marking the code as 'depends on BROKEN' now, it will no longer be covered by CI testing. If any users remain, they can keep patching out the dependency but are more likely to run into regressions.
The big-endian ARMv5 support (CONFIG_CPU_ENDIAN_BE32) in contrast is still used on Intel IXP4xx platform, and is the only currently supported mode there, so this one can still be enabled.
There is no timeline for actually removing the code at this point, we will likely debate this if we ever remove IXP4xx support on arm, or big-endian support on ARM64.
--- arch/arm/mm/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/arm/mm/Kconfig +2 -1
@@ -778,7 +778,8 @@ config CPU_LITTLE_ENDIAN space builds. config CPU_BIG_ENDIAN - bool "Build big-endian kernel" + bool "Build big-endian kernel (DEPRECATED)" + depends on ARCH_MULTI_V5 || BROKEN depends on !LD_IS_LLD help Say Y if you plan on running a kernel in big-endian mode.
Signature · 1 line
2.39.5
PATCH v2 7/19 ARM: update DEPRECATED_PARAM_STRUCT removal timeline
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
This configuration option is for the older boot method that preceeded ATAGS. This was scheduled for removal back in 2001, but the removal never happened, presumably because nobody cared enough to actually do it, not because there are any users left.
Add "(DEPRECATED)' to the Kconfig line and update the timeline so we can remove it next year along with the other options that are not scheduled for that timeframe.
--- arch/arm/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/Kconfig +2 -2
@@ -1401,11 +1401,11 @@ config ATAGS it is either converted to DT or removed. config DEPRECATED_PARAM_STRUCT - bool "Provide old way to pass kernel parameters" + bool "Provide old way to pass kernel parameters (DEPRECATED)" depends on ATAGS help This was deprecated in 2001 and announced to live on for 5 years. - Some old boot loaders still use this way. + It is now scheduled for removal in early 2027. # Compressed boot loader in ROM. Yes, we really want to ask about # TEXT and BSS so we preserve their values in the config files.
Signature · 1 line
2.39.5
PATCH v2 8/19 ARM: s3c64xx: extend deprecation schedule
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Mark Brown is still using this machine for regular work, so it should not be removed as originally scheduled.
Give the platform another year, with the option to extend it further based on the state of ATAGS support next year.
I expect that we end up removing all of s3c64xx when either Mark has moved his test setup to other hardware, or when all other ATAGS based machines are getting removed.
--- arch/arm/mach-s3c/Kconfig.s3c64xx | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
arch/arm/mach-s3c/Kconfig.s3c64xx +11 -4
@@ -23,10 +23,17 @@ menuconfig ARCH_S3C64XX help Samsung S3C64XX series based systems - The platform is deprecated and scheduled for removal. Please reach to - the maintainers of the platform and [email protected] if - you still use it. - Without such feedback, the platform will be removed after 2024. + The use of ATAGS based board files is on its way out, and + the only remaining S3C64xx machine in the kernel (Wolfson + Cragganmore 6410) relies on this, without any realistic way + to migrate it to devicetree. + + Support for S3C64XX will be kept until the 2027 LTS kernel + release and may be removed in early 2028. + + Please reach out to the maintainers of the platform and + [email protected] if you use any additional + s3c64xx machines based on devicetree. if ARCH_S3C64XX
Signature · 1 line
2.39.5
PATCH v2 9/19 ARM: update FPE_NWFPE help text
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The help text is seriously outdated and predates the introduction of VFP floating point units that were available as early as some ARM926 based systems.
Change the help text to reflect that this is now a legacy feature and that it will go away along with OABI support in the future.
--- arch/arm/Kconfig | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
arch/arm/Kconfig +6 -6
@@ -1651,16 +1651,16 @@ menu "Floating point emulation" comment "At least one emulation must be selected" config FPE_NWFPE - bool "NWFPE math emulation" + bool "NWFPE math emulation (DEPRECATED)" depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL help Say Y to include the NWFPE floating point emulator in the kernel. - This is necessary to run most binaries. Linux does not currently - support floating point hardware so you need to say Y here even if - your machine has an FPA or floating point co-processor podule. - You may say N here if you are going to load the Acorn FPEmulator - early in the bootup. + This is only used on OABI userspace binaries, either using a + pure OABI (!CONFIG_AEABI) kernel, or the OABI emulation. + + Support for NWFPE will be removed in the future when OABI + support is removed. config FPE_NWFPE_XP bool "Support extended precision"
Signature · 1 line
2.39.5
PATCH v2 10/19 ARM: mark IWMMXT as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
With no remaining users and support getting removed from future compilers, there seems little point in keeping iwmmxt around much longer.
On the other hand, the iwmmxt support in the kernel rarely gets in the way, so there is little cost, so set a removal date of early 2027 for the moment. If anyone is still using this, it can be extended as long there is binutils support.
--- arch/arm/Kconfig | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
arch/arm/Kconfig +11 -3
@@ -513,13 +513,21 @@ config PLAT_VERSATILE source "arch/arm/mm/Kconfig" config IWMMXT - bool "Enable iWMMXt support" - depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK - default y if PXA27x || PXA3xx || ARCH_MMP + bool "Enable iWMMXt support (DEPRECATED)" + depends on PXA27x || PXA3xx || ARCH_MMP help Enable support for iWMMXt context switching at run time if running on a CPU that supports it. + Machines that actually support this feature are very rare, + and support is deprecated in new gcc-14. While there were a + few applications that used this in the past, none are known + to still do so. + + If you use this, please send a patch to remove the + deprecation, otherwise this will be removed in early + 2027. + if !MMU source "arch/arm/Kconfig-nommu" endif
Signature · 1 line
2.39.5
PATCH v2 11/19 ARM: mark ARCH_DOVE as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The Marvell Armada 510 (Dove) platform is supported both as devicetree and atags/boardfile variants, with varying degrees of hardware support.
Russell was the last known user of the board file version, and there are very few users overall. Unless Russell still needs this variant, let's remove after the next LTS kernel, leaving the CONFIG_MACH_DOVE variant with devicetree.
--- arch/arm/mach-dove/Kconfig | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
arch/arm/mach-dove/Kconfig +6 -2
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0 menuconfig ARCH_DOVE - bool "Marvell Dove" if ARCH_MULTI_V7 + bool "Marvell Dove (DEPRECATED)" if ARCH_MULTI_V7 depends on ATAGS select CPU_PJ4 select GPIOLIB
@@ -11,7 +11,11 @@ menuconfig ARCH_DOVE select PM_GENERIC_DOMAINS if PM select PCI_QUIRKS if PCI help - Support for the Marvell Dove SoC 88AP510 + Support for the Marvell Dove SoC 88AP510 using board files. + + Support for this machine will be removed in early 2027, unless + there is a strong reason to keep it. Users should migrate to + the devicetree-enabled version (CONFIG_MACH_DOVE) instead. if ARCH_DOVE
Signature · 1 line
2.39.5
PATCH v2 12/19 ARM: PXA: mark remaining board files as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
In the 2021 board file removal, the gumstix and sharpsl support was left around in order to make it easier to convert more of the PXA platform to device tree, given that both platforms had some level of support in qemu.
As far as I can tell, nobody has worked on additional DT conversion in that time, and qemu has in turn deprecated the entire PXA platform.
Schedule the remaining board files for removal now, as they are unlikely to be of any help in the future. If anyone wants to revive support for these machines, they can obviously still contribute device tree based code and work on updating the corresponding drivers.
Any drivers that are only usable on legacy PXA board files can also get removed along with the boards, or saved by adding devicetree support.
--- arch/arm/configs/pxa_defconfig | 4 ---- arch/arm/mach-pxa/Kconfig | 10 ++++++++-- 2 files changed, 8 insertions(+), 6 deletions(-)
arch/arm/configs/pxa_defconfig +0 -4
@@ -16,10 +16,6 @@ CONFIG_PROFILING=y CONFIG_KEXEC=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y -CONFIG_ARCH_GUMSTIX=y -CONFIG_PXA_SHARPSL=y -CONFIG_MACH_AKITA=y -CONFIG_MACH_BORZOI=y CONFIG_ARCH_FORCE_MAX_ORDER=8 CONFIG_CMDLINE="root=/dev/ram0 ro" CONFIG_CPU_FREQ=y
arch/arm/mach-pxa/Kconfig +8 -2
@@ -58,12 +58,15 @@ if ATAGS comment "Legacy board files" config ARCH_GUMSTIX - bool "Gumstix XScale 255 boards" + bool "Gumstix XScale 255 boards (DEPRECATED)" select PXA25x help Say Y here if you intend to run this kernel on Basix, Connex, ws-200ax, ws-400ax systems + Support for this machine will go away in early 2027, + unless it gets converted to device tree. + choice prompt "Gumstix Carrier/Expansion Board" depends on ARCH_GUMSTIX
@@ -77,7 +80,7 @@ config GUMSTIX_AM300EPD endchoice config PXA_SHARPSL - bool "SHARP Zaurus SL-5600, SL-C7xx and SL-Cxx00 Models" + bool "SHARP Zaurus SL-5600, SL-C7xx and SL-Cxx00 Models (DEPRECATED)" select SHARP_PARAM select SHARP_SCOOP help
@@ -87,6 +90,9 @@ config PXA_SHARPSL SL-C3000 (Spitz), SL-C3100 (Borzoi) or SL-C6000x (Tosa) handheld computer. + Support for these machines will go away in early 2027, + unless they get converted to device tree. + config PXA_SHARPSL_DETECT_MACH_ID bool "Detect machine ID at run-time in the decompressor" depends on PXA_SHARPSL
Signature · 1 line
2.39.5
PATCH v2 13/19 ARM: orion5x: mark all board files as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Conversion of the old orion5x board files to devicetree has stalled over the past few years, so it seems better to remove the remaining ones in order to allow cleaning up the device drivers.
Debian has previously removed the orion/kirkwood kernel binary from the armel distro, but building custom kernels from the Debian source code should keep working, so removing the board files after the 6.12 release ensures that this remains possible for the Debian Trixie release, assuming this will use the 6.12 LTS kernel.
Jeremy Peper still plans to convert the Terastation 2 Pro to devicetree in the future, but that can be done even after it is removed.
--- arch/arm/configs/multi_v5_defconfig | 9 ------ arch/arm/configs/mvebu_v5_defconfig | 9 ------ arch/arm/configs/orion5x_defconfig | 9 ------ arch/arm/mach-orion5x/Kconfig | 47 +++++++++++++++++++++++------ 4 files changed, 37 insertions(+), 37 deletions(-)
arch/arm/configs/multi_v5_defconfig +0 -9
@@ -22,17 +22,8 @@ CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_ARCH_ORION5X=y CONFIG_MACH_RD88F5182_DT=y -CONFIG_MACH_KUROBOX_PRO=y -CONFIG_MACH_DNS323=y -CONFIG_MACH_TS209=y -CONFIG_MACH_TERASTATION_PRO2=y -CONFIG_MACH_LINKSTATION_PRO=y CONFIG_MACH_LINKSTATION_MINI=y -CONFIG_MACH_TS409=y -CONFIG_MACH_TS78XX=y -CONFIG_MACH_MV2120=y CONFIG_MACH_D2NET_DT=y -CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_VERSATILE=y
arch/arm/configs/mvebu_v5_defconfig +0 -9
@@ -10,17 +10,8 @@ CONFIG_ARCH_MVEBU=y CONFIG_MACH_KIRKWOOD=y CONFIG_ARCH_ORION5X=y CONFIG_MACH_RD88F5182_DT=y -CONFIG_MACH_KUROBOX_PRO=y -CONFIG_MACH_DNS323=y -CONFIG_MACH_TS209=y -CONFIG_MACH_TERASTATION_PRO2=y -CONFIG_MACH_LINKSTATION_PRO=y CONFIG_MACH_LINKSTATION_MINI=y -CONFIG_MACH_TS409=y -CONFIG_MACH_TS78XX=y -CONFIG_MACH_MV2120=y CONFIG_MACH_D2NET_DT=y -CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y
arch/arm/configs/orion5x_defconfig +0 -9
@@ -10,16 +10,7 @@ CONFIG_ARCH_MULTI_V5=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_ORION5X=y CONFIG_MACH_RD88F5182_DT=y -CONFIG_MACH_KUROBOX_PRO=y -CONFIG_MACH_DNS323=y -CONFIG_MACH_TS209=y -CONFIG_MACH_TERASTATION_PRO2=y -CONFIG_MACH_LINKSTATION_PRO=y CONFIG_MACH_LINKSTATION_MINI=y -CONFIG_MACH_TS409=y -CONFIG_MACH_TS78XX=y -CONFIG_MACH_MV2120=y -CONFIG_MACH_NET2BIG=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=y
arch/arm/mach-orion5x/Kconfig +37 -10
126 lines not on this page · raw message
Signature · 1 line
2.39.5
PATCH v2 14/19 ARM: mark mach-sa1100 as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Most of the old StrongARM1100 machines were removed two years ago as part of a wider cleanup, the remaining four were left either because someone showed interest in converting them to devicetree, or because they were still supported by qemu and therefore useful to keep the platform alive.
None of the devicetree conversion actually happened, and qemu has marked the platform as deprecated, so do the same in the kernel now.
If anyone is still running one of these four machines and planning to keep updating their kernels, please speak up now so we can adapt the plans as needed.
If nobody is found using StrongARM1100 any more, it can be removing during 2027, leaving 6.12-LTS as the last longterm support kernel for it.
--- arch/arm/mach-sa1100/Kconfig | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
arch/arm/mach-sa1100/Kconfig +4 -1
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only menuconfig ARCH_SA1100 - bool "SA11x0 Implementations" + bool "SA11x0 Implementations (DEPRECATED)" depends on ARCH_MULTI_V4 && !(ARCH_MULTI_V4T || ARCH_MULTI_V5) depends on !(ARCH_MOXART || ARCH_GEMINI) depends on ATAGS
@@ -20,6 +20,9 @@ menuconfig ARCH_SA1100 help Support for StrongARM 11x0 based boards. + Support for these machines will go away in 2027, + unless there are any remaining users that speak up. + if ARCH_SA1100 config SA1100_ASSABET
Signature · 1 line
2.39.5
PATCH v2 15/19 ARM: mark RiscPC as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
This platform is the oldest still supported machine, dating back to the original 1994 ARM610 version. The only currently supported configuration uses an ARMv4 StrongARM but still requires building for ARMv3 because of the board design not supporting 16-bit data access.
ARMv3 support has been removed in gcc-9, and the gcc-8 release is already old but still supported for building the kernel.
The only set of machines that lacks support for 16-bit load/store instructions (Alpha EV5 and older) was recently removed from the kernel.
Since there is little hope of this being maintainable much longer, plan to remove it in early 2027 while it is still expected to mostly work.
--- arch/arm/mach-rpc/Kconfig | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
arch/arm/mach-rpc/Kconfig +4 -1
@@ -1,5 +1,5 @@ config ARCH_RPC - bool "RiscPC" + bool "RiscPC (DEPRECATED)" depends on ARCH_MULTI_V4 && !(ARCH_MULTI_V4T || ARCH_MULTI_V5) depends on !(ARCH_FOOTBRIDGE || ARCH_SA1100 || ARCH_MOXART || ARCH_GEMINI) depends on !CC_IS_CLANG && GCC_VERSION < 90100 && GCC_VERSION >= 60000
@@ -19,3 +19,6 @@ config ARCH_RPC help On the Acorn Risc-PC, Linux can support the internal IDE disk and CD-ROM interface, serial and parallel port, and the floppy drive. + + Support for these machines will go away in 2027, + unless there are any remaining users that speak up.
Signature · 1 line
2.39.5
PATCH v2 16/19 ARM: mark footbridge as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Along with RiscPC and SA1100, these are the last remaining Intel StrongARM machines. The Corel NetWinder used to be particular popular in the late 1990s, but was discontinued during the bankruptcy of rebel.com in 2001. The other machine is the DEC (later Intel) EBSA285 evaluation board that was made in small numbers in 1997 for software developers.
The footbridge/netwinder platform was the main target for the first Debian 2.0 "Hamm" release on the Arm architecture back in 1998, but was dropped in Debian 6.0 "Squeeze" in 2011, which only supported ARMv4T and higher with the EABI based ports as ARMv4 hardware had fallen already out of use by that time.
--- arch/arm/mach-footbridge/Kconfig | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
arch/arm/mach-footbridge/Kconfig +5 -2
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only menuconfig ARCH_FOOTBRIDGE - bool "FootBridge Implementations" + bool "FootBridge Implementations (DEPRECATED)" depends on ARCH_MULTI_V4 && !(ARCH_MULTI_V4T || ARCH_MULTI_V5) depends on !(ARCH_MOXART || ARCH_GEMINI || ARCH_SA1100) depends on ATAGS
@@ -12,7 +12,10 @@ menuconfig ARCH_FOOTBRIDGE select NEED_MACH_MEMORY_H help Support for systems based on the DC21285 companion chip - ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder. + ("FootBridge"), used in the EBSA285 and the Rebel NetWinder. + + Support for these machines will go away in 2027, + unless there are any remaining users that speak up. if ARCH_FOOTBRIDGE
Signature · 1 line
2.39.5
PATCH v2 17/19 ARM: mark Cortex-M3/M4/M7 based boards as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The Cortex-M3/M4/M7 cores were designed as a replacement for the earlier ARM7TDMI and ARM9TDMI microarchitectures used in older microcontrollers.
At the moment, Linux can run these cores either when they are integrated into a larger SoC, or as standalone microcontrollers. While there was a lot of development work going into Cortex-M support from 2011 to 2016, this largely stopped when it became clear that Zephyr and other RTOS had taken over that market. To date, the only Cortex-M based based microcontroller boards supported upstream are reference implementations.
Schedule these for removal after the next LTS kernel, so if any users remain that want to update their kernels, they can stay on that version for a few years before having to maintain the platform support out of tree.
--- arch/arm/Kconfig | 8 ++++++-- arch/arm/mach-at91/Kconfig | 4 +++- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-stm32/Kconfig | 14 ++++++++------ 4 files changed, 20 insertions(+), 10 deletions(-)
arch/arm/Kconfig +6 -2
@@ -471,7 +471,7 @@ source "arch/arm/mach-zynq/Kconfig" # ARMv7-M architecture config ARCH_LPC18XX - bool "NXP LPC18xx/LPC43xx" + bool "NXP LPC18xx/LPC43xx (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARCH_HAS_RESET_CONTROLLER select ARM_AMBA
@@ -481,8 +481,10 @@ config ARCH_LPC18XX Support for NXP's LPC18xx Cortex-M3 and LPC43xx Cortex-M4 high performance microcontrollers. + This platform is scheduled for removal in early 2027 + config ARCH_MPS2 - bool "ARM MPS2 platform" + bool "ARM MPS2 platform (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARM_AMBA select CLKSRC_MPS2
@@ -493,6 +495,8 @@ config ARCH_MPS2 Please, note that depends which Application Note is used memory map for the platform may vary, so adjustment of RAM base might be needed. + This platform is scheduled for removal in early 2027 + # Definitions to make life easier config ARCH_ACORN bool
arch/arm/mach-at91/Kconfig +3 -1
@@ -15,13 +15,15 @@ menuconfig ARCH_AT91 if ARCH_AT91 config SOC_SAMV7 - bool "SAM Cortex-M7 family" if ARM_SINGLE_ARMV7M + bool "SAM Cortex-M7 family (DEPRECATED)" if ARM_SINGLE_ARMV7M select COMMON_CLK_AT91 select PINCTRL_AT91 help Select this if you are using an SoC from Microchip's SAME7, SAMS7 or SAMV7 families. + This platform is scheduled for removal in early 2027 + config SOC_SAMA5D2 bool "SAMA5D2 family" depends on ARCH_MULTI_V7
arch/arm/mach-imx/Kconfig +3 -1
@@ -219,12 +219,14 @@ config SOC_IMX7ULP This enables support for Freescale i.MX7 Ultra Low Power processor. config SOC_IMXRT - bool "i.MXRT support" + bool "i.MXRT support (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARMV7M_SYSTICK if ARM_SINGLE_ARMV7M help This enables support for Freescale i.MXRT Crossover processor. + This platform is scheduled for removal in early 2027 + config SOC_VF610 bool "Vybrid Family VF610 support" select ARM_GIC if ARCH_MULTI_V7
arch/arm/mach-stm32/Kconfig +8 -6
@@ -14,30 +14,32 @@ menuconfig ARCH_STM32 select STM32_EXTI if ARM_SINGLE_ARMV7M select STM32_FIREWALL help - Support for STMicroelectronics STM32 processors. + Support for STMicroelectronics STM32MP1 processors using Cortex-A7 + cores. Note that support for the earlier Cortex-M based variants + is deprecated and scheduled for removal in early 2027. if ARCH_STM32 if ARM_SINGLE_ARMV7M config MACH_STM32F429 - bool "STMicroelectronics STM32F429" + bool "STMicroelectronics STM32F429 (DEPRECATED)" default y config MACH_STM32F469 - bool "STMicroelectronics STM32F469" + bool "STMicroelectronics STM32F469 (DEPRECATED)" default y config MACH_STM32F746 - bool "STMicroelectronics STM32F746" + bool "STMicroelectronics STM32F746 (DEPRECATED)" default y config MACH_STM32F769 - bool "STMicroelectronics STM32F769" + bool "STMicroelectronics STM32F769 (DEPRECATED)" default y config MACH_STM32H743 - bool "STMicroelectronics STM32H743" + bool "STMicroelectronics STM32H743 (DEPRECATED)" default y endif # ARMv7-M
Signature · 1 line
2.39.5
PATCH v2 18/19 ARM: mark axxia platform as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The Axxia platform was initially upstream by Anders Berg for LSI and later Avago, but this included only support for I2C and reset drivers, while most of the interesting bits (network, pci, rapidio, usb, ...) or the arm64 platform support were never merged.
The downstream kernel was maintained by Intel up to linux-5.15 when the product line was discontinued. Known users include Nokia and Ericsson, but both of them use kernels derived from the out-of-tree drivers rather than the upstream version, and will be able to continue doing that even when the rudimentary mainline support is gone.
Mark it as deprecated for removal after the next LTS kernel.
--- arch/arm/mach-axxia/Kconfig | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/arm/mach-axxia/Kconfig +3 -1
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0 config ARCH_AXXIA - bool "LSI Axxia platforms" + bool "LSI Axxia platforms (DEPRECATED)" depends on ARCH_MULTI_V7 && ARM_LPAE select ARM_AMBA select ARM_GIC
@@ -13,3 +13,5 @@ config ARCH_AXXIA The LSI Axxia platforms require a Flattened Device Tree to be passed to the kernel. + + This platform is scheduled for removal in early 2027
Signature · 1 line
2.39.5
PATCH v2 19/19 ARM: mark mv78xx0 support as deprecated
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Only one machine remains supported and was kept in 2022 for the Debian_on_Buffalo project that was still using this, with plans to convert it to devicetree.
The conversion never happened, and Debian_on_Buffalo does not provide kernels later than linux-6.1, so it is unlikely to still be useful for a DT conversion in the future.
Mark the platform for deprecation after the next LTS kernel, which should give any remaining users a few more years of bugfixes.
--- arch/arm/mach-mv78xx0/Kconfig | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/arm/mach-mv78xx0/Kconfig +3 -1
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only menuconfig ARCH_MV78XX0 - bool "Marvell MV78xx0" + bool "Marvell MV78xx0 (DEPRECATED)" depends on ARCH_MULTI_V5 depends on CPU_LITTLE_ENDIAN depends on ATAGS
@@ -14,6 +14,8 @@ menuconfig ARCH_MV78XX0 Support for the following Marvell MV78xx0 series SoCs: MV781x0, MV782x0. + This platform is scheduled for removal in early 2027. + if ARCH_MV78XX0 config MACH_TERASTATION_WXL
Signature · 1 line
2.39.5
Re: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
In reply to Arnd BergmannHi, Arnd,
Quoted 5 lines · Arnd Bergmann
Following the deprecation of big-endian ARMv8 mode in
arch/arm64in commit1cf89b6bf660("arm64:Kconfig: MakeCPU_BIG_ENDIANdepend on BROKEN"), this does the same for ARMv7 (and v6), leaving the code around but disabled by default: There are no known products that make use of this mode any more, and it only hangs around for testing that it still works.
Nice! Getting rid of ARM big-endian support is long overdue in my opinion. The patch looks good to me, although see below for a couple minor questions.
Quoted 9 lines
At the moment, there are no known bugs with big-endian ARMv7 mode, but it does break occasionally and require someone to fix it. By marking the code as 'depends on BROKEN' now, it will no longer be covered by CI testing. If any users remain, they can keep patching out the dependency but are more likely to run into regressions.
The big-endian ARMv5 support (
CONFIG_CPU_ENDIAN_BE32) in contrast is still used on Intel IXP4xx platform, and is the only currently supported mode there, so this one can still be enabled.
If IXP4xx is the only known remaining user, would it make sense for CPU_BIG_ENDIAN to instead depend on ARCH_IXP4XX || BROKEN? Is BE32 mode known to work correctly on any other platforms?
Ethan
Re: [PATCH v2 04/19] ARM: deprecate support for ARM1136r0
In reply to Arnd BergmannQuoted 25 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
This CPU revision remains a special case as it is now incompatible with
CONFIG_SMP. Only the Nokia N8x0 is used in practice, and even that one is fairly rare these days, so let's plan to remove all of them after the 2026 LTS kernel release.Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/mach-imx/Kconfig | 5 ++++- arch/arm/mach-omap2/Kconfig | 15 ++++++++++++--- arch/arm/mach-versatile/Kconfig | 5 ++++- arch/arm/mm/Kconfig | 2 ++ 4 files changed, 22 insertions(+), 5 deletions(-)arch/arm/mach-imx/Kconfig +0
-1@@ -40,13 +40,16 @@ if ARCH_MULTI_V6 comment "ARM1136 platforms" config SOC_IMX31 - bool "i.MX31 support"
arch/arm/mach-imx/Kconfig if ARCH_MULTI_V6 · line 52
Quoted 10 lines
arch/arm/mach-imx/Kconfig +4
-0+ bool "i.MX31 support (DEPRECATED)" depends on !SMP select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. +
It's a nice SoC, long time ago its watchdog driver was broken in upstream and never got fixed unfortunately...
Quoted 83 lines
arch/arm/mach-imx/Kconfig +0
-0config SOC_IMX35 bool "i.MX35 support" select CPU_ARM1136R1arch/arm/mach-omap2/Kconfig +12
-3@@ -207,18 +207,24 @@ comment "OMAP Core Type" depends on ARCH_OMAP2 config SOC_OMAP2420 - bool "OMAP2420 support" + bool "OMAP2420 support (DEPRECATED)" depends on ARCH_OMAP2 default y select OMAP_DM_SYSTIMER select OMAP_DM_TIMER select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP2430 - bool "OMAP2430 support" + bool "OMAP2430 support (DEPRECATED)" depends on ARCH_OMAP2 default y select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP3430 bool "OMAP3430 support"@@ -249,11 +255,14 @@ config MACH_NOKIA_N810_WIMAX bool config MACH_NOKIA_N8X0 - bool "Nokia N800/N810" + bool "Nokia N800/N810 (DEPRECATED)" depends on SOC_OMAP2420 default y select MACH_NOKIA_N810 select MACH_NOKIA_N810_WIMAX + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. endmenuarch/arm/mach-versatile/Kconfig +4
-1@@ -110,11 +110,14 @@ config INTEGRATOR_CM1026EJS select CPU_ARM1026 config INTEGRATOR_CM1136JFS - bool "Integrator/CM1136JF-S core module" + bool "Integrator/CM1136JF-S core module (DEPRECATED)" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 depends on !SMP select CPU_ARM1136R0 + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"arch/arm/mm/Kconfig +2
-0@@ -410,6 +410,8 @@ config CPU_ARM1136R0 help These early revisions of ARM1136 lack support for the ARMv6k extensions for multiprocessing. + Support for this revision is scheduled for removal + from the kernel in early 2027. config CPU_ARM1136R1 bool
Signature · 2 lines
Best wishes, Vladimir
Re: [PATCH v2 17/19] ARM: mark Cortex-M3/M4/M7 based boards as deprecated
In reply to Arnd BergmannQuoted 39 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Cortex-M3/M4/M7 cores were designed as a replacement for the earlier ARM7TDMI and ARM9TDMI microarchitectures used in older microcontrollers.
At the moment, Linux can run these cores either when they are integrated into a larger SoC, or as standalone microcontrollers. While there was a lot of development work going into Cortex-M support from 2011 to 2016, this largely stopped when it became clear that Zephyr and other RTOS had taken over that market. To date, the only Cortex-M based based microcontroller boards supported upstream are reference implementations.
Schedule these for removal after the next LTS kernel, so if any users remain that want to update their kernels, they can stay on that version for a few years before having to maintain the platform support out of tree.
Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 8 ++++++-- arch/arm/mach-at91/Kconfig | 4 +++- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-stm32/Kconfig | 14 ++++++++------ 4 files changed, 20 insertions(+), 10 deletions(-)arch/arm/Kconfig +1
-1@@ -471,7 +471,7 @@ source "arch/arm/mach-zynq/Kconfig" # ARMv7-M architecture config ARCH_LPC18XX - bool "NXP LPC18xx/LPC43xx" + bool "NXP LPC18xx/LPC43xx (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARCH_HAS_RESET_CONTROLLER select ARM_AMBA
arch/arm/Kconfig config ARCH_LPC18XX · line 485
Quoted 5 lines
arch/arm/Kconfig +2
-0@@ -481,8 +481,10 @@ config ARCH_LPC18XX Support for NXP's LPC18xx Cortex-M3 and LPC43xx Cortex-M4 high performance microcontrollers. + This platform is scheduled for removal in early 2027 +
Quoted 99 lines
arch/arm/Kconfig +3
-1config ARCH_MPS2 - bool "ARM MPS2 platform" + bool "ARM MPS2 platform (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARM_AMBA select CLKSRC_MPS2@@ -493,6 +495,8 @@ config ARCH_MPS2 Please, note that depends which Application Note is used memory map for the platform may vary, so adjustment of RAM base might be needed. + This platform is scheduled for removal in early 2027 + # Definitions to make life easier config ARCH_ACORN boolarch/arm/mach-at91/Kconfig +3
-1@@ -15,13 +15,15 @@ menuconfig ARCH_AT91 if ARCH_AT91 config SOC_SAMV7 - bool "SAM Cortex-M7 family" if ARM_SINGLE_ARMV7M + bool "SAM Cortex-M7 family (DEPRECATED)" if ARM_SINGLE_ARMV7M select COMMON_CLK_AT91 select PINCTRL_AT91 help Select this if you are using an SoC from Microchip's SAME7, SAMS7 or SAMV7 families. + This platform is scheduled for removal in early 2027 + config SOC_SAMA5D2 bool "SAMA5D2 family" depends on ARCH_MULTI_V7arch/arm/mach-imx/Kconfig +3
-1@@ -219,12 +219,14 @@ config SOC_IMX7ULP This enables support for Freescale i.MX7 Ultra Low Power processor. config SOC_IMXRT - bool "i.MXRT support" + bool "i.MXRT support (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARMV7M_SYSTICK if ARM_SINGLE_ARMV7M help This enables support for Freescale i.MXRT Crossover processor. + This platform is scheduled for removal in early 2027 + config SOC_VF610 bool "Vybrid Family VF610 support" select ARM_GIC if ARCH_MULTI_V7arch/arm/mach-stm32/Kconfig +8
-6@@ -14,30 +14,32 @@ menuconfig ARCH_STM32 select STM32_EXTI if ARM_SINGLE_ARMV7M select STM32_FIREWALL help - Support for STMicroelectronics STM32 processors. + Support for STMicroelectronics STM32MP1 processors using Cortex-A7 + cores. Note that support for the earlier Cortex-M based variants + is deprecated and scheduled for removal in early 2027. if ARCH_STM32 if ARM_SINGLE_ARMV7M config MACH_STM32F429 - bool "STMicroelectronics STM32F429" + bool "STMicroelectronics STM32F429 (DEPRECATED)" default y config MACH_STM32F469 - bool "STMicroelectronics STM32F469" + bool "STMicroelectronics STM32F469 (DEPRECATED)" default y config MACH_STM32F746 - bool "STMicroelectronics STM32F746" + bool "STMicroelectronics STM32F746 (DEPRECATED)" default y config MACH_STM32F769 - bool "STMicroelectronics STM32F769" + bool "STMicroelectronics STM32F769 (DEPRECATED)" default y config MACH_STM32H743 - bool "STMicroelectronics STM32H743" + bool "STMicroelectronics STM32H743 (DEPRECATED)" default y endif # ARMv7-M
Signature · 2 lines
Best wishes, Vladimir
Re: [PATCH v2 05/19] ARM: turn CONFIG_ATAGS off by default
In reply to Arnd BergmannHi, Arnd,
Looks good to me, though I noticed a few small issues.
Quoted 8 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Only a very small number of machines remain that rely on traditional board files with the ATAGS boot data instead of devicetree, and we have not accepted new ones for a decade.
Quoted 7 lines
Most of the remaining ones are on their way out of the kernel, but the
Kconfigoption that controls ATAGS is still enabled by default.To reflect the actual status of ATAGS support and alert the remaining users of upstream and out-of-tree platforms with this, chanyge it to being default-disabled and
nit: change*
Quoted 5 lines
add a dependency on
CONFIG_EXPERT.The board specific defconfig files that rely on ATAGS are changed to turn on both EXPERT and ATAGS if they were not doing thath already, and the ones that explicitly
nit: that*
arch/arm/configs/stm32_defconfig CONFIG_ARCH_STM32=y · line 24
Quoted 11 lines
turned it off before no longer need to.
arch/arm/configs/stm32_defconfig +2
-1@@ -20,7 +20,8 @@ CONFIG_ARCH_STM32=y CONFIG_CPU_V7M_NUM_IRQ=240 CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x90000000 -# CONFIG_ATAGS is not set +CONFIG_FLASH_MEM_BASE=0x08000000 +CONFIG_FLASH_SIZE=0x00200000
^ These shouldn't be here - they depend on CPU_ARM740T || CPU_ARM946E || CPU_ARM940T, and they were manually removed previously. If they got added when you did make savedefconfig, I'm not sure why, given that dependency.
these issues are fixed)
Ethan
Re: [PATCH v2 18/19] ARM: mark axxia platform as deprecated
In reply to Arnd BergmannHi, Arnd,
Quoted 1 line · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
All of these patches have this line at the beginning but were sent from your kernel.org email - did something go wrong with git send-email?
Quoted 4 lines
The Axxia platform was initially upstream by Anders Berg for LSI and later Avago, but this included only support for I2C and reset drivers, while most of the interesting bits (network, pci, rapidio, usb, ...) or the arm64 platform support were never merged.
Given the incomplete state of this platform, removing it makes complete sense to me.
arch/arm/mach-axxia/Kconfig line 4
Quoted 4 lines
config
ARCH_AXXIAarch/arm/mach-axxia/Kconfig +1
-1- bool "LSI Axxia platforms" + bool "LSI Axxia platforms (DEPRECATED)" depends on ARCH_MULTI_V7 && ARM_LPAE
The dependency on LPAE reminded me of two other 32-bit ARM platforms with lots of memory: Calxeda Midway and Highbank. Is anyone still using those? Maybe they could be removed, since people seem to want to remove highmem:
https://lwn.net/Articles/813201/
https://static.linaro.org/connect/lvc20/presentations/LVC20-106-0.pdf
arch/arm/mach-axxia/Kconfig config ARCH_AXXIA · line 17
Quoted 8 lines
select
ARM_AMBA
selectARM_GICarch/arm/mach-axxia/Kconfig +2
-0@@ -13,3 +13,5 @@ config ARCH_AXXIA The LSI Axxia platforms require a Flattened Device Tree to be passed to the kernel. + + This platform is scheduled for removal in early 2027
microscopic nit: missing period
Ethan
Re: [PATCH v2 11/19] ARM: mark ARCH_DOVE as deprecated
In reply to Arnd BergmannQuoted 42 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Marvell Armada 510 (Dove) platform is supported both as devicetree and atags/boardfile variants, with varying degrees of hardware support.
Russell was the last known user of the board file version, and there are very few users overall. Unless Russell still needs this variant, let's remove after the next LTS kernel, leaving the
CONFIG_MACH_DOVEvariant with devicetree.Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/mach-dove/Kconfig | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)arch/arm/mach-dove/Kconfig +6
-3@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0 menuconfig ARCH_DOVE - bool "Marvell Dove" if ARCH_MULTI_V7 + bool "Marvell Dove (DEPRECATED)" if ARCH_MULTI_V7 depends on ATAGS select CPU_PJ4 select GPIOLIB@@ -11,7 +11,11 @@ menuconfig ARCH_DOVE select PM_GENERIC_DOMAINS if PM select PCI_QUIRKS if PCI help - Support for the Marvell Dove SoC 88AP510 + Support for the Marvell Dove SoC 88AP510 using board files. + + Support for this machine will be removed in early 2027, unless + there is a strong reason to keep it. Users should migrate to + the devicetree-enabled version (CONFIG_MACH_DOVE) instead. if ARCH_DOVE --
Quoted 2 lines
2.39.5
Re: [PATCH v2 07/19] ARM: update DEPRECATED_PARAM_STRUCT removal timeline
In reply to Arnd BergmannHi, Arnd,
Quoted 4 lines · Arnd Bergmann
This configuration option is for the older boot method that preceeded ATAGS. This was scheduled for removal back in 2001, but the removal never happened, presumably because nobody cared enough to actually do it, not because there are any users left.
Only netwinder_defconfig selects this option. Do the most recent NetWinder firmware versions actually need it? (LinusW, do you know this?) If not, can't we just drop it entirely?
Ethan
Re: [PATCH v2 07/19] ARM: update DEPRECATED_PARAM_STRUCT removal timeline
Quoted 11 lines · Ethan Nelson-Moore
Hi, Arnd,
Quoted 4 lines · Arnd Bergmann
This configuration option is for the older boot method that preceeded ATAGS. This was scheduled for removal back in 2001, but the removal never happened, presumably because nobody cared enough to actually do it, not because there are any users left.
Only
netwinder_defconfigselects this option. Do the most recent NetWinder firmware versions actually need it? (LinusW, do you know this?) If not, can't we just drop it entirely?
If all StrongARM platforms are on the way out after the LTS kernel, I don't see a need to remove this any earlier, even if the chance that it's still needed is low.
Arnd
Re: [PATCH v2 18/19] ARM: mark axxia platform as deprecated
In reply to Ethan Nelson-MooreQuoted 8 lines · Ethan Nelson-Moore
Hi, Arnd,
Quoted 1 line · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
All of these patches have this line at the beginning but were sent from your kernel.org email - did something go wrong with git send-email?
I should fix this, but it's been like this for a while after I had patch emails get rejected too much for coming from my arndb.de domain.
Quoted 11 lines
arch/arm/mach-axxia/Kconfig line 4
Quoted 4 lines
config
ARCH_AXXIAarch/arm/mach-axxia/Kconfig +1
-1- bool "LSI Axxia platforms" + bool "LSI Axxia platforms (DEPRECATED)" depends on ARCH_MULTI_V7 && ARM_LPAEThe dependency on LPAE reminded me of two other 32-bit ARM platforms with lots of memory: Calxeda Midway and Highbank. Is anyone still using those? Maybe they could be removed, since people seem to want to remove highmem:
https://lwn.net/Articles/813201/
https://static.linaro.org/connect/lvc20/presentations/LVC20-106-0.pdf
Andre Przywara used to use those for testing, I don't think anyone else has powered them on for a while, see
https://lore.kernel.org/all/[email protected]/
If it gets in the way, or Andre gets tired of maintaining it, we can remove it, until then I would keep it. Axxia is different because it's neither maintained nor functional.
There are a few more platforms that need highmem for the time being:
- TI keystone2 has users and is well maintained, so this will stay as long as we can justify holding up highmem removal for it. This one has a unique way of dealing with coherent DMA that requires LPAE and possibly highmem.
- Renesas R-Car M1 need lpae support for (IIRC) >1GB configurations, and I have a prototype patch to make that one work with a modified virt_to_phys() implementation.
- Amazon/Annapurna Alpine is similar to Axxia in the current state of upstream support, but has someone working on an OpenWRT port using the downstream patches. The OpenWRT supported devices all have 2GB or less.
A few others need highmem for large memory configs with more than 2GB of RAM but would stay working for the common configurations with 2GB or less, using CONFIG_VMSPLIT_2G_OPT.
Arnd
Re: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
In reply to Ethan Nelson-MooreQuoted 6 lines · Ethan Nelson-Moore
Quoted 6 lines
At the moment, there are no known bugs with big-endian ARMv7 mode, but it does break occasionally and require someone to fix it. By marking the code as 'depends on BROKEN' now, it will no longer be covered by CI testing. If any users remain, they can keep patching out the dependency but are more likely to run into regressions.
Quoted 7 lines
Quoted 3 lines
The big-endian ARMv5 support (
CONFIG_CPU_ENDIAN_BE32) in contrast is still used on Intel IXP4xx platform, and is the only currently supported mode there, so this one can still be enabled.If IXP4xx is the only known remaining user, would it make sense for
CPU_BIG_ENDIANto instead depend onARCH_IXP4XX|| BROKEN? Is BE32 mode known to work correctly on any other platforms?
This is essentially what we have, just expressed the other way round:
all ARMv4/v4t/v5 platforms depend on CONFIG_CPU_LITTLE_ENDIAN, except for IXP4xx, which depends on CONFIG_CPU_BIG_ENDIAN.
Arnd
Re: [PATCH v2 05/19] ARM: turn CONFIG_ATAGS off by default
In reply to Ethan Nelson-MooreQuoted 6 lines · Ethan Nelson-Moore
Quoted 6 lines
arch/arm/configs/stm32_defconfig +0
-0@@ -20,7 +20,8 @@ CONFIG_ARCH_STM32=y CONFIG_CPU_V7M_NUM_IRQ=240 CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x90000000
Quoted 8 lines
arch/arm/configs/stm32_defconfig CONFIG_ARCH_STM32=y · line 24
Quoted 3 lines
arch/arm/configs/stm32_defconfig +2
-1-# CONFIG_ATAGS is not set +CONFIG_FLASH_MEM_BASE=0x08000000 +CONFIG_FLASH_SIZE=0x00200000^ These shouldn't be here - they depend on
CPU_ARM740T||CPU_ARM946E||CPU_ARM940T, and they were manually removed previously. If they got added when you did make savedefconfig, I'm not sure why, given that dependency.
This likely happened during a rebase
Quoted 2 lines
Reviewed-by Ethan Nelson-Moore <[email protected]> (assumingthese issues are fixed)
Thanks, fixed all now for v3
Arnd
Re: [PATCH v2 17/19] ARM: mark Cortex-M3/M4/M7 based boards as deprecated
In reply to Arnd BergmannQuoted 24 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Cortex-M3/M4/M7 cores were designed as a replacement for the earlier ARM7TDMI and ARM9TDMI microarchitectures used in older microcontrollers.
At the moment, Linux can run these cores either when they are integrated into a larger SoC, or as standalone microcontrollers. While there was a lot of development work going into Cortex-M support from 2011 to 2016, this largely stopped when it became clear that Zephyr and other RTOS had taken over that market. To date, the only Cortex-M based based microcontroller boards supported upstream are reference implementations.
Schedule these for removal after the next LTS kernel, so if any users remain that want to update their kernels, they can stay on that version for a few years before having to maintain the platform support out of tree.
Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 8 ++++++-- arch/arm/mach-at91/Kconfig | 4 +++- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-stm32/Kconfig | 14 ++++++++------ 4 files changed, 20 insertions(+), 10 deletions(-)
[..]
Quoted 7 lines
arch/arm/mach-at91/Kconfig +0
-0@@ -15,13 +15,15 @@ menuconfig ARCH_AT91 if ARCH_AT91
arch/arm/mach-at91/Kconfig menuconfig ARCH_AT91 · line 25
Quoted 10 lines
arch/arm/mach-at91/Kconfig +2
-1config SOC_SAMV7 - bool "SAM Cortex-M7 family" if ARM_SINGLE_ARMV7M + bool "SAM Cortex-M7 family (DEPRECATED)" if ARM_SINGLE_ARMV7M select COMMON_CLK_AT91 select PINCTRL_AT91 help Select this if you are using an SoC from Microchip's SAME7, SAMS7 or SAMV7 families. + This platform is scheduled for removal in early 2027
arch/arm/mach-at91/Kconfig menuconfig ARCH_AT91 · line 29
Quoted 4 lines
arch/arm/mach-at91/Kconfig +1
-0+ config SOC_SAMA5D2 bool "SAMA5D2 family" depends on ARCH_MULTI_V7
[..]
Thanks, regards,
Nicolas
Re: [PATCH v2 01/19] ARM: use CONFIG_AEABI by default everywhere
In reply to Arnd BergmannQuoted 9 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
On ARMv4 and ARMv5, the default is still to build for OABI, with
CONFIG_AEABIdisabled, even though distros and toolchains no longer support OABI as a target.Change the default to EABI for all architecture levels and change the defconfig entries as follows:
Quoted 6 lines
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig(at91_dt, collie, ep93xx, gemini, h3600, imx_v4_v5, integrator, jornada,
For at91_dt, EABI was explicitly enabled (see below)...
Quoted 12 lines
moxart,
multi_v4t, omap1) were likely not usable with either OABI or EABI and now use EABI instead implicitly, making it more likely that they could work.Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 15 ++++++--------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/assabet_defconfig | 1 + arch/arm/configs/at91_dt_defconfig | 1 -
[..]
arch/arm/configs/at91_dt_defconfig CONFIG_SOC_AT91SAM9=y · line 23
Quoted 12 lines
arch/arm/configs/at91_dt_defconfig +0
-1@@ -18,7 +18,6 @@ CONFIG_SOC_AT91SAM9=y CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y
As AEABI is by default to y:
[..]
Thanks, best regards,
Nicolas
Re: [PATCH v2 01/19] ARM: use CONFIG_AEABI by default everywhere
Quoted 11 lines · Nicolas Ferre
Quoted 8 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig(at91_dt, collie, ep93xx, gemini, h3600, imx_v4_v5, integrator, jornada,For
at91_dt, EABI was explicitly enabled (see below)...
Right. I don't know how I got to that list originally, but looking again now, the only configs that I see using OABI but not NWFPE here are spear3xx and spear6xx. I've updated the text now, thanks!
Arnd
Re: [PATCH v2 17/19] ARM: mark Cortex-M3/M4/M7 based boards as deprecated
In reply to Arnd BergmannQuoted 25 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Cortex-M3/M4/M7 cores were designed as a replacement for the earlier ARM7TDMI and ARM9TDMI microarchitectures used in older microcontrollers.
At the moment, Linux can run these cores either when they are integrated into a larger SoC, or as standalone microcontrollers. While there was a lot of development work going into Cortex-M support from 2011 to 2016, this largely stopped when it became clear that Zephyr and other RTOS had taken over that market. To date, the only Cortex-M based based microcontroller boards supported upstream are reference implementations.
Schedule these for removal after the next LTS kernel, so if any users remain that want to update their kernels, they can stay on that version for a few years before having to maintain the platform support out of tree.
Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 8 ++++++-- arch/arm/mach-at91/Kconfig | 4 +++- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-stm32/Kconfig | 14 ++++++++------ 4 files changed, 20 insertions(+), 10 deletions(-)
[snip]
Quoted 7 lines
config
ARCH_MPS2arch/arm/Kconfig +1
-1- bool "ARM MPS2 platform" + bool "ARM MPS2 platform (DEPRECATED)" depends on ARM_SINGLE_ARMV7M select ARM_AMBA select CLKSRC_MPS2
arch/arm/Kconfig config ARCH_MPS2 · line 502
Quoted 8 lines
arch/arm/Kconfig +2
-0@@ -493,6 +495,8 @@ config ARCH_MPS2 Please, note that depends which Application Note is used memory map for the platform may vary, so adjustment of RAM base might be needed. + This platform is scheduled for removal in early 2027 + # Definitions to make life easier config ARCH_ACORN bool
Thanks
Vladimir
Re: [PATCH v2 09/19] ARM: update FPE_NWFPE help text
In reply to Arnd BergmannQuoted 7 lines · Arnd Bergmann
The help text is seriously outdated and predates the introduction of VFP floating point units that were available as early as some ARM926 based systems.
Change the help text to reflect that this is now a legacy feature and that it will go away along with OABI support in the future.
Indeed NWFPE was initially added in order to be able to execute pre-existing binaries from even earlier systems.
Once soft-float became available in the toolchain, the netwinder userspace was rebuilt, and NWFPE became largely unnecessary.
All of this happened in the early 2000's.
Quoted 2 lines
Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
Regards,
Ralph
Re: [PATCH v2 07/19] ARM: update DEPRECATED_PARAM_STRUCT removal timeline
In reply to Arnd BergmannQuoted 4 lines · Arnd Bergmann
Quoted 3 lines · Ethan Nelson-Moore
Hi, Arnd,
On Wed, Jul 1, 2026 at 2:25 PM Arnd Bergmann <[email protected]> wrote:
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
This configuration option is for the older boot method that preceeded ATAGS. This was scheduled for removal back in 2001, but the removal never happened, presumably because nobody cared enough to actually do it, not because there are any users left.
Only
netwinder_defconfigselects this option. Do the most recent NetWinder firmware versions actually need it? (LinusW, do you know this?) If not, can't we just drop it entirely?
Support for ATAG was added in firmware v2.0.6 in roughly Jan 1999, meanwhile the most recent firmware is v2.3.3 (still 20+ years old).
It is quite safe to disable support for the older parameter method.
Quoted 3 lines
If all StrongARM platforms are on the way out after the LTS kernel, I don't see a need to remove this any earlier, even if the chance that it's still needed is low.
Also agree with this, might as well remove it all in one go.
Regards,
Ralph
Re: [PATCH v2 01/19] ARM: use CONFIG_AEABI by default everywhere
In reply to Arnd BergmannQuoted 19 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
On ARMv4 and ARMv5, the default is still to build for OABI, with
CONFIG_AEABIdisabled, even though distros and toolchains no longer support OABI as a target.Change the default to EABI for all architecture levels and change the defconfig entries as follows:
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig (at91_dt, collie, ep93xx, gemini, h3600,imx_v4_v5, integrator, jornada, moxart,multi_v4t, omap1) were likely not usable with either OABI or EABI and now use EABI instead implicitly, making it more likely that they could work.
Quoted 1 line
Acked-by Linus Walleij <[email protected]>
Quoted 609 lines
Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 15 ++++++--------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/assabet_defconfig | 1 + arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/bcm2835_defconfig | 1 - arch/arm/configs/clps711x_defconfig | 1 - arch/arm/configs/collie_defconfig | 1 - arch/arm/configs/davinci_all_defconfig | 1 - arch/arm/configs/dove_defconfig | 1 - arch/arm/configs/ep93xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 1 + arch/arm/configs/gemini_defconfig | 1 - arch/arm/configs/h3600_defconfig | 1 - arch/arm/configs/hisi_defconfig | 1 - arch/arm/configs/imx_v4_v5_defconfig | 1 - arch/arm/configs/integrator_defconfig | 1 - arch/arm/configs/ixp4xx_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 1 - arch/arm/configs/keystone_defconfig | 1 - arch/arm/configs/lpc32xx_defconfig | 1 - arch/arm/configs/mmp2_defconfig | 1 - arch/arm/configs/moxart_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 1 - arch/arm/configs/multi_v5_defconfig | 1 - arch/arm/configs/mv78xx0_defconfig | 2 -- arch/arm/configs/mvebu_v5_defconfig | 1 - arch/arm/configs/mxs_defconfig | 1 - arch/arm/configs/neponset_defconfig | 1 + arch/arm/configs/netwinder_defconfig | 1 + arch/arm/configs/nhk8815_defconfig | 1 - arch/arm/configs/omap1_defconfig | 2 -- arch/arm/configs/orion5x_defconfig | 2 -- arch/arm/configs/pxa168_defconfig | 2 -- arch/arm/configs/pxa3xx_defconfig | 2 -- arch/arm/configs/pxa910_defconfig | 2 -- arch/arm/configs/pxa_defconfig | 1 - arch/arm/configs/rpc_defconfig | 1 + arch/arm/configs/spear13xx_defconfig | 1 - arch/arm/configs/spitz_defconfig | 1 - arch/arm/configs/versatile_defconfig | 1 - arch/arm/configs/vt8500_v6_v7_defconfig | 1 - arch/arm/configs/wpcm450_defconfig | 1 - 44 files changed, 11 insertions(+), 53 deletions(-)arch/arm/Kconfig +6
-9@@ -1153,17 +1153,14 @@ config ARM_PATCH_IDIV config AEABI bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \ !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG - default CPU_V7 || CPU_V7M || CPU_V6 || CPU_V6K || CC_IS_CLANG + default y help - This option allows for the kernel to be compiled using the latest - ARM ABI (aka EABI). This is only useful if you are using a user - space environment that is also compiled with EABI. + The Arm EABI is the default ABI on all modern Linux + distributions, replacing the obsolete and "OABI" that was + commonly used on ARMv4 distributions before ca. 2013. - Since there are major incompatibilities between the legacy ABI and - EABI, especially with regard to structure member alignment, this - option also changes the kernel syscall calling convention to - disambiguate both ABIs and allow for backward compatibility support - (selected with CONFIG_OABI_COMPAT). + Everyone should enable this, as support for OABI user space + was dropped in gcc-4.8 and most distributions after ca. 2013. config OABI_COMPAT bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"arch/arm/configs/am200epdkit_defconfig +0
-1@@ -7,7 +7,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y -CONFIG_AEABI=y # CONFIG_OABI_COMPAT is not set CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=yarch/arm/configs/aspeed_g4_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_ASPEED=y CONFIG_MACH_ASPEED_G4=y CONFIG_VMSPLIT_2G=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_JUMP_LABEL=yarch/arm/configs/assabet_defconfig +1
-0@@ -5,6 +5,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y +# CONFIG_AEABI is not set CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram" CONFIG_FPE_NWFPE=y CONFIG_PM=yarch/arm/configs/at91_dt_defconfig +0
-1@@ -18,7 +18,6 @@ CONFIG_SOC_AT91SAM9=y CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/axm55xx_defconfig +0
-1@@ -38,7 +38,6 @@ CONFIG_PCIE_AXXIA=y CONFIG_SMP=y CONFIG_NR_CPUS=16 CONFIG_HOTPLUG_CPU=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/bcm2835_defconfig +0
-1@@ -25,7 +25,6 @@ CONFIG_CRASH_DUMP=y CONFIG_ARCH_MULTI_V6=y CONFIG_ARCH_BCM=y CONFIG_ARCH_BCM2835=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_KEXEC=y CONFIG_CPU_FREQ=yarch/arm/configs/clps711x_defconfig +0
-1@@ -6,7 +6,6 @@ CONFIG_RD_LZMA=y CONFIG_EXPERT=y CONFIG_JUMP_LABEL=y CONFIG_PARTITION_ADVANCED=y -CONFIG_AEABI=y # CONFIG_COREDUMP is not set CONFIG_SLUB_TINY=y CONFIG_NET=yarch/arm/configs/collie_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_COLLIE=y CONFIG_CMDLINE="noinitrd root=/dev/mtdblock2 rootfstype=jffs2 fbcon=rotate:1" -CONFIG_FPE_NWFPE=y CONFIG_PM=y # CONFIG_SWAP is not set CONFIG_SLUB_TINY=yarch/arm/configs/davinci_all_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_ARCH_DAVINCI=y CONFIG_ARCH_DAVINCI_DA850=y CONFIG_DAVINCI_MUX_DEBUG=y CONFIG_DAVINCI_MUX_WARNINGS=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/dove_defconfig +0
-1@@ -7,7 +7,6 @@ CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_DOVE=y CONFIG_MACH_CM_A510=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/ep93xx_defconfig +0
-1@@ -18,7 +18,6 @@ CONFIG_MACH_EDB9315=y CONFIG_MACH_EDB9315A=y CONFIG_MACH_TS72XX=y CONFIG_MACH_VISION_EP9307=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyAM0,115200 root=/dev/nfs ip=bootp" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/footbridge_defconfig +1
-0@@ -11,6 +11,7 @@ CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=yarch/arm/configs/gemini_defconfig +0
-1@@ -11,7 +11,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_GEMINI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_CMDLINE="console=ttyS0,115200n8" CONFIG_PM=yarch/arm/configs/h3600_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_H3600=y # CONFIG_CPU_FREQ_STAT is not set -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_UNIX=yarch/arm/configs/hisi_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_ARCH_HIP04=y CONFIG_ARCH_HIX5HD2=y CONFIG_SMP=y CONFIG_NR_CPUS=16 -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/imx_v4_v5_defconfig +0
-1@@ -15,7 +15,6 @@ CONFIG_ARCH_MXC=y CONFIG_SOC_IMX1=y CONFIG_SOC_IMX25=y CONFIG_SOC_IMX27=y -CONFIG_AEABI=y CONFIG_PM_DEBUG=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/integrator_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_ARCH_INTEGRATOR=y CONFIG_ARCH_INTEGRATOR_AP=y CONFIG_INTEGRATOR_IMPD1=y CONFIG_ARCH_INTEGRATOR_CP=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyAM0,38400n8 root=/dev/nfs ip=bootp" CONFIG_CPU_FREQ=yarch/arm/configs/ixp4xx_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_IXP4XX=y CONFIG_CPU_BIG_ENDIAN=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyS0,115200" CONFIG_STRICT_KERNEL_RWX=y CONFIG_STRICT_MODULE_RWX=yarch/arm/configs/jornada720_defconfig +0
-1@@ -5,7 +5,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_JORNADA720=y CONFIG_SA1100_JORNADA720_SSP=y -CONFIG_FPE_NWFPE=y CONFIG_PM=y CONFIG_MODULES=y CONFIG_NET=yarch/arm/configs/keystone_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_PCI_KEYSTONE=y CONFIG_SMP=y CONFIG_HOTPLUG_CPU=y CONFIG_ARM_PSCI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_VFP=y CONFIG_NEON=yarch/arm/configs/lpc32xx_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_LPC32XX=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CMDLINE="console=ttyS0,115200n81 root=/dev/ram0"arch/arm/configs/mmp2_defconfig +0
-1@@ -4,7 +4,6 @@ CONFIG_PREEMPT=y CONFIG_LOG_BUF_SHIFT=14 # CONFIG_BLK_DEV_BSG is not set CONFIG_ARCH_MMP=y -CONFIG_AEABI=y CONFIG_MACH_MMP2_DT=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS2,38400 mem=128M user_debug=255 earlyprintk" CONFIG_VFP=yarch/arm/configs/moxart_defconfig +0
-1@@ -16,7 +16,6 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MOXART=y CONFIG_MACH_UC7112LX=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y # CONFIG_SWAP is not setarch/arm/configs/multi_v4t_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_INTEGRATOR_IMPD1=y CONFIG_INTEGRATOR_CM720T=y CONFIG_INTEGRATOR_CM920T=y CONFIG_INTEGRATOR_CM922T_XA10=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CPU_IDLE=y CONFIG_ARM_CPUIDLE=yarch/arm/configs/multi_v5_defconfig +0
-1@@ -36,7 +36,6 @@ CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/mv78xx0_defconfig +0
-2@@ -11,9 +11,7 @@ CONFIG_ARCH_MULTI_V5=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MV78XX0=y CONFIG_MACH_TERASTATION_WXL=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/mvebu_v5_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_MACH_MV2120=y CONFIG_MACH_D2NET_DT=y CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/mxs_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_PERF_EVENTS=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MXS=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/neponset_defconfig +1
-0@@ -11,6 +11,7 @@ CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y CONFIG_CMDLINE="console=ttySA0,38400n8 cpufreq=221200 rw root=/dev/mtdblock2 mtdparts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) mem=32M noinitrd initrd=0xc0800000,3M" CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_PM=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/netwinder_defconfig +1
-0@@ -4,6 +4,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_DEPRECATED_PARAM_STRUCT=y CONFIG_CMDLINE="root=0x801" CONFIG_FPE_NWFPE=yarch/arm/configs/nhk8815_defconfig +0
-1@@ -12,7 +12,6 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_NOMADIK=y CONFIG_MACH_NOMADIK_8815NHK=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_SWAP is not setarch/arm/configs/omap1_defconfig +0
-2@@ -28,9 +28,7 @@ CONFIG_MACH_OMAP_PALMTE=y CONFIG_MACH_SX1=y CONFIG_MACH_NOKIA770=y CONFIG_MACH_AMS_DELTA=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=1f03 rootfstype=jffs2" -CONFIG_FPE_NWFPE=y # CONFIG_SUSPEND is not set CONFIG_PM=y CONFIG_MODULES=yarch/arm/configs/orion5x_defconfig +0
-2@@ -20,10 +20,8 @@ CONFIG_MACH_TS409=y CONFIG_MACH_TS78XX=y CONFIG_MACH_MV2120=y CONFIG_MACH_NET2BIG=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/pxa168_defconfig +0
-2@@ -3,11 +3,9 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ_IDLE=y CONFIG_HIGH_RES_TIMERS=y CONFIG_PREEMPT=y -CONFIG_AEABI=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_ARCH_MMP=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.2.100:/nfsroot/ ip=192.168.2.101:192.168.2.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=128M" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=yarch/arm/configs/pxa3xx_defconfig +0
-2@@ -7,9 +7,7 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_MACH_PXA3XX_DT=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=64M debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_PACKET=yarch/arm/configs/pxa910_defconfig +0
-2@@ -10,8 +10,6 @@ CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_BLK_DEV_BSG is not set -CONFIG_AEABI=y -CONFIG_FPE_NWFPE=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=yarch/arm/configs/pxa_defconfig +0
-1@@ -20,7 +20,6 @@ CONFIG_ARCH_GUMSTIX=y CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y -CONFIG_AEABI=y CONFIG_ARCH_FORCE_MAX_ORDER=8 CONFIG_CMDLINE="root=/dev/ram0 ro" CONFIG_CPU_FREQ=yarch/arm/configs/rpc_defconfig +1
-0@@ -7,6 +7,7 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_RPC=y CONFIG_CPU_SA110=y CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=yarch/arm/configs/spear13xx_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_MACH_SPEAR1340=y CONFIG_SMP=y # CONFIG_SMP_ON_UP is not set # CONFIG_ARM_CPU_TOPOLOGY is not set -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=yarch/arm/configs/spitz_defconfig +0
-1@@ -11,7 +11,6 @@ CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/mtdblock2 rootfstype=jffs2 debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=yarch/arm/configs/versatile_defconfig +0
-1@@ -6,7 +6,6 @@ CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_CMDLINE="root=1f03 mem=32M" CONFIG_FPE_NWFPE=yarch/arm/configs/vt8500_v6_v7_defconfig +0
-1@@ -8,7 +8,6 @@ CONFIG_ARM_ERRATA_720789=y CONFIG_ARM_ERRATA_754322=y CONFIG_ARM_ERRATA_775420=y CONFIG_HAVE_ARM_ARCH_TIMER=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/wpcm450_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_PROFILING=y CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_CPU_DCACHE_WRITETHROUGH=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=ySignature · 1 line
2.39.5
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [PATCH v2 16/19] ARM: mark footbridge as deprecated
In reply to Arnd BergmannQuoted 46 lines · Arnd Bergmann
Along with RiscPC and SA1100, these are the last remaining Intel StrongARM machines. The Corel NetWinder used to be particular popular in the late 1990s, but was discontinued during the bankruptcy of rebel.com in 2001. The other machine is the DEC (later Intel) EBSA285 evaluation board that was made in small numbers in 1997 for software developers.
The footbridge/netwinder platform was the main target for the first Debian 2.0 "Hamm" release on the Arm architecture back in 1998, but was dropped in Debian 6.0 "Squeeze" in 2011, which only supported ARMv4T and higher with the EABI based ports as ARMv4 hardware had fallen already out of use by that time.
Cc Linus Walleij <[email protected]>Cc Russell King <[email protected]>Cc Ralph Siemsen <[email protected]>Acked-by Linus Walleij <[email protected]>Acked-by Marc Zyngier <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>---
arch/arm/mach-footbridge/Kconfig| 7 +++++--1 file changed, 5 insertions(+), 2 deletions(-)arch/arm/mach-footbridge/Kconfig +0
-0@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-onlymenuconfig
ARCH_FOOTBRIDGEarch/arm/mach-footbridge/Kconfig +1
-1- bool "FootBridge Implementations" + bool "FootBridge Implementations (DEPRECATED)"depends on ARCH_MULTI_V4 && !(ARCH_MULTI_V4T || ARCH_MULTI_V5) depends on !(ARCH_MOXART || ARCH_GEMINI || ARCH_SA1100) depends on ATAGSarch/arm/mach-footbridge/Kconfig +4
-1@@ -12,7 +12,10 @@ menuconfig ARCH_FOOTBRIDGE select NEED_MACH_MEMORY_H help Support for systems based on the DC21285 companion chip - ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder. + ("FootBridge"), used in the EBSA285 and the Rebel NetWinder. + + Support for these machines will go away in 2027, + unless there are any remaining users that speak up.
Quoted 2 lines
if
ARCH_FOOTBRIDGE
Speaking for NetWinder, although it is sad to let it go, the reality is there have been no active users in years. This is based on the mailing list being silent (other than spam). And the trickle of emails I used to get about netwinder has also ended for many years. So with that:
Regards,
Ralph
Alexandre Belloni
maintainerRe: [PATCH v2 02/19] ARM: limit OABI support to StrongARM CPUs
In reply to Arnd BergmannQuoted 100 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
As discussed on the mailing lists, there is no way to build OABI userspace binaries any more since gcc-4.8, and now support is also getting dropped in binutils, which will make it impossible to build pure OABI kernels at some point in the future.
I found no evidence of anyone still sing OABI userspace on embedded systems that keep getting kernel updates, but there are a few desktop-class machines that date back to the 1990s using Intel StrongARM processors that were supported by old versions of Debian, Red Hat or the official Corel Netwinder distribution.
Add a much stricter
Kconfigdependency for both native OABI andOABI_COMPATenabled kernels, only allowing either of them to be selected when building a kernel that targets a StrongARM based machine.Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 14 +++++++------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 2 +- arch/arm/configs/neponset_defconfig | 2 +- arch/arm/configs/versatile_defconfig | 1 - 6 files changed, 9 insertions(+), 12 deletions(-)arch/arm/Kconfig +7
-7@@ -1151,8 +1151,7 @@ config ARM_PATCH_IDIV code to do integer division. config AEABI - bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \ - !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG + bool "Use the ARM EABI to compile the kernel" if CPU_SA110 || CPU_SA1100 default y help The Arm EABI is the default ABI on all modern Linux@@ -1162,9 +1161,13 @@ config AEABI Everyone should enable this, as support for OABI user space was dropped in gcc-4.8 and most distributions after ca. 2013. + Support for OABI mode will be removed from the kernel + once Intel StrongARM CPUs are phased out. + config OABI_COMPAT bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)" depends on AEABI && !THUMB2_KERNEL + depends on CPU_SA110 || CPU_SA1100 help This option preserves the old syscall interface along with the new (ARM EABI) one. It also provides a compatibility layer to@@ -1177,11 +1180,8 @@ config OABI_COMPAT selected, since there is no way yet to sensibly distinguish between calling conventions during filtering. - If you know you'll be using only pure EABI user space then you - can say N here. If this option is not selected and you attempt - to execute a legacy ABI binary then the result will be - UNPREDICTABLE (in fact it can be predicted that it won't work - at all). If in doubt say N. + Support for OABI_COMPAT will be removed from the kernel + once Intel StrongARM CPUs are phased out. config ARCH_SELECT_MEMORY_MODEL def_bool yarch/arm/configs/am200epdkit_defconfig +0
-1@@ -7,7 +7,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y -# CONFIG_OABI_COMPAT is not set CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/axm55xx_defconfig +0
-1@@ -38,7 +38,6 @@ CONFIG_PCIE_AXXIA=y CONFIG_SMP=y CONFIG_NR_CPUS=16 CONFIG_HOTPLUG_CPU=y -CONFIG_OABI_COMPAT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/footbridge_defconfig +0
-0
arch/arm/configs/footbridge_defconfig CONFIG_ARCH_MULTI_V4=y · line 14
Quoted 7 lines
arch/arm/configs/footbridge_defconfig +1
-1@@ -9,9 +9,9 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y -# CONFIG_AEABI is not set
I'm not objecting to the change this reordering is not directly related to the current patch, maybe this should be squashed in 1/19
Quoted 8 lines
arch/arm/configs/footbridge_defconfig +0
-0CONFIG_MODULES=y CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=yarch/arm/configs/neponset_defconfig +0
-0
arch/arm/configs/neponset_defconfig CONFIG_ARCH_MULTI_V4=y · line 14
Quoted 10 lines
arch/arm/configs/neponset_defconfig +1
-1@@ -6,12 +6,12 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y CONFIG_ASSABET_NEPONSET=y +# CONFIG_AEABI is not set CONFIG_ZBOOT_ROM_TEXT=0x80000 CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y CONFIG_CMDLINE="console=ttySA0,38400n8 cpufreq=221200 rw root=/dev/mtdblock2 mtdparts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) mem=32M noinitrd initrd=0xc0800000,3M" CONFIG_FPE_NWFPE=y -# CONFIG_AEABI is not set
Ditto
Quoted 18 lines
arch/arm/configs/neponset_defconfig +0
-0CONFIG_PM=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/versatile_defconfig +0
-1@@ -6,7 +6,6 @@ CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_VERSATILE=y -CONFIG_OABI_COMPAT=y CONFIG_CMDLINE="root=1f03 mem=32M" CONFIG_FPE_NWFPE=y CONFIG_VFP=ySignature · 1 line
2.39.5
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [PATCH v2 02/19] ARM: limit OABI support to StrongARM CPUs
Quoted 14 lines · Alexandre Belloni
arch/arm/configs/footbridge_defconfig CONFIG_ARCH_MULTI_V4=y · line 14
Quoted 8 lines · Arnd Bergmann
arch/arm/configs/footbridge_defconfig +1
-1@@ -9,9 +9,9 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y -# CONFIG_AEABI is not setI'm not objecting to the change this reordering is not directly related to the current patch, maybe this should be squashed in 1/19
I've dropped these changes now, I don't think they were intentional at the time.
Arnd
Alexandre Belloni
maintainerRe: [PATCH v2 03/19] ARM: rework ARM11 CPU selection logic
In reply to Arnd BergmannQuoted 15 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Support for SMP on ARM1136r0 has been broken for a while, and nobody is working on fixing it. I had a plan to change ARMv6 support to no longer coexist in a common kernel with ARMv7 CPUs but instead ARMv5 and below. This would have addressed the problem, but after a recent mailing list discussion, we concluded that an easier approach is to just forbid ARM1136r0 CPU support on SMP-enabled kernels.
This mainly affects users of the Nokia N800/N810 tablets using an OMAP2420 SoC, which is the only commercial product with an ARM1136r0 that is still supported by the kernel.
The other machines that are still in the same hardware catogory are:
Quoted 8 lines
- TI OMAP2420 H4 reference board
- TI OMAP2430 SDP software development platform
- Freescale/NXP i.MX31 Lite Development Kit
- Buglabs i.MX31 Bug 1.x prototype
- Arm Integrator/AP with CM1136JF-S core moduleTo my knowledge, none of these have any actual users aside from reference boards being used more easily test the platforms.
There is a missing "to" in this sentence ;)
Quoted 180 lines
There are also a few ARM1136r1 machines, which implement the ARMv6K SMP support (barriers, atomics and TLS):
- Eukrea CPUIMX35 reference platform
- Freescale/NXP i.MX35 Product Development Kit
- ARM Integrator/CP/IM-LT3 with ARM1136J Core Tile
- ARM Realview/EB with ARM1136J Core TileAgain, these are mainly reference implementations rather than actual products, but since they support ARMv6K, they should continue to work correctly in SMP-enabled kernels. For the ARM Core Tile, I have not found a datasheet but instead use the revision based on what the respective virtual models report.
All the other ARMv6 platforms use an ARM1176 with ARMv6K, VMSAv7 and Trustzone support.
To avoid the broken configuration, annotate the ARM1136 based machines with specific
CPU_ARM1136R0orCPU_ARM1136R2symbols inKconfigand make the r0 variants depend on !SMP.Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig.platforms | 2 +- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-omap2/Kconfig | 3 ++- arch/arm/mach-versatile/Kconfig | 10 +++++----- arch/arm/mm/Kconfig | 24 +++++++++++++++++++++++- 5 files changed, 34 insertions(+), 9 deletions(-)arch/arm/Kconfig.platforms +1
-1@@ -33,7 +33,7 @@ config ARCH_MULTI_V4_V5 config ARCH_MULTI_V6 bool "ARMv6 based platforms (ARM11)" select ARCH_MULTI_V6_V7 - select CPU_V6K + select CPU_ARM1176 config ARCH_MULTI_V7 bool "ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)"arch/arm/mach-imx/Kconfig +3
-1@@ -41,13 +41,15 @@ comment "ARM1136 platforms" config SOC_IMX31 bool "i.MX31 support" - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor config SOC_IMX35 bool "i.MX35 support" + select CPU_ARM1136R1 select MXC_AVIC help This enables support for Freescale i.MX35 processorarch/arm/mach-omap2/Kconfig +2
-1@@ -8,8 +8,9 @@ config OMAP_HWMOD config ARCH_OMAP2 bool "TI OMAP2" depends on ARCH_MULTI_V6 + depends on !SMP select ARCH_OMAP2PLUS - select CPU_V6 + select CPU_ARM1136R0 select OMAP_HWMOD select SOC_HAS_OMAP2_SDRCarch/arm/mach-versatile/Kconfig +5
-5@@ -113,7 +113,8 @@ config INTEGRATOR_CM1136JFS bool "Integrator/CM1136JF-S core module" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"@@ -135,7 +136,7 @@ config INTEGRATOR_CTB36 bool "Integrator/CTB36 (ARM1136JF-S) core tile" depends on ARCH_INTEGRATOR_CP depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 config ARCH_CINTEGRATOR depends on ARCH_INTEGRATOR_CP@@ -182,7 +183,7 @@ config MACH_REALVIEW_EB config REALVIEW_EB_ARM1136 bool "Support ARM1136J(F)-S Tile" depends on MACH_REALVIEW_EB && ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 help Enable support for the ARM1136 tile fitted to the Realview(R) Emulation Baseboard platform.@@ -201,11 +202,10 @@ config REALVIEW_EB_A9MP Enable support for the Cortex-A9MPCore tile fitted to the Realview(R) Emulation Baseboard platform. -# ARMv6 CPU without K extensions, but does have the new exclusive ops config MACH_REALVIEW_PB1176 bool "Support RealView(R) Platform Baseboard for ARM1176JZF-S" depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1176 select HAVE_TCM help Include support for the ARM(R) RealView(R) Platform Baseboard forarch/arm/mm/Kconfig +23
-1@@ -376,6 +376,7 @@ config CPU_PJ4B # ARMv6 config CPU_V6 bool + depends on !SMP select CPU_32v6 select CPU_ABRT_EV6 select CPU_CACHE_V6@@ -386,7 +387,6 @@ config CPU_V6 select CPU_PABRT_V6 select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU - select SMP_ON_UP if SMP # ARMv6k config CPU_V6K@@ -403,6 +403,28 @@ config CPU_V6K select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU +config CPU_ARM1136R0 + bool + select CPU_V6 + depends on !SMP + help + These early revisions of ARM1136 lack support for the + ARMv6k extensions for multiprocessing. + +config CPU_ARM1136R1 + bool + select CPU_V6K + help + Later revisions of ARM1136 add ARMv6k (atomics, barriers + and TLS register) in addition to the features from r0. + +config CPU_ARM1176 + bool + select CPU_V6K + help + ARM1176 implements ARMv6k, VMSAv7 and Trustzone in + addition to the ARMv6 baseline. + # ARMv7 and ARMv8 architectures config CPU_V7 boolSignature · 1 line
2.39.5
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [PATCH v2 03/19] ARM: rework ARM11 CPU selection logic
Quoted 6 lines · Alexandre Belloni
Quoted 3 lines · Arnd Bergmann
To my knowledge, none of these have any actual users aside from reference boards being used more easily test the platforms.
There is a missing "to" in this sentence ;)
Fixed, thanks!
Arnd
Re: [PATCH v2 13/19] ARM: orion5x: mark all board files as deprecated
In reply to Arnd BergmannQuoted 6 lines · Arnd Bergmann
Debian has previously removed the orion/kirkwood kernel binary from the armel distro, but building custom kernels from the Debian source code should keep working, so removing the board files after the 6.12 release ensures that this remains possible for the Debian Trixie release, assuming this will use the 6.12 LTS kernel.
I noticed this paragraph is outdated and have now replaced it with
| Debian and OpenWRT no longer support orion5x, and buildroot | could keep using linux-7.3-LTS for a few more years.
Arnd
Re: [PATCH v2 17/19] ARM: mark Cortex-M3/M4/M7 based boards as deprecated
In reply to Arnd BergmannQuoted 17 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Cortex-M3/M4/M7 cores were designed as a replacement for the earlier ARM7TDMI and ARM9TDMI microarchitectures used in older microcontrollers.
At the moment, Linux can run these cores either when they are integrated into a larger SoC, or as standalone microcontrollers. While there was a lot of development work going into Cortex-M support from 2011 to 2016, this largely stopped when it became clear that Zephyr and other RTOS had taken over that market. To date, the only Cortex-M based based microcontroller boards supported upstream are reference implementations.
Schedule these for removal after the next LTS kernel, so if any users remain that want to update their kernels, they can stay on that version for a few years before having to maintain the platform support out of tree.
Quoted 5 lines
Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/Kconfig | 8 ++++++-- arch/arm/mach-at91/Kconfig | 4 +++- arch/arm/mach-imx/Kconfig | 4 +++-
for imx part.
Re: [PATCH v2 01/19] ARM: use CONFIG_AEABI by default everywhere
In reply to Arnd BergmannHi,
Quoted 19 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
On ARMv4 and ARMv5, the default is still to build for OABI, with
CONFIG_AEABIdisabled, even though distros and toolchains no longer support OABI as a target.Change the default to EABI for all architecture levels and change the defconfig entries as follows:
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig (at91_dt, collie, ep93xx, gemini, h3600,imx_v4_v5, integrator, jornada, moxart,multi_v4t, omap1) were likely not usable with either OABI or EABI and now use EABI instead implicitly, making it more likely that they could work.
Quoted 2 lines
Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
Quoted 608 lines
--- arch/arm/Kconfig | 15 ++++++--------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/assabet_defconfig | 1 + arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/bcm2835_defconfig | 1 - arch/arm/configs/clps711x_defconfig | 1 - arch/arm/configs/collie_defconfig | 1 - arch/arm/configs/davinci_all_defconfig | 1 - arch/arm/configs/dove_defconfig | 1 - arch/arm/configs/ep93xx_defconfig | 1 - arch/arm/configs/footbridge_defconfig | 1 + arch/arm/configs/gemini_defconfig | 1 - arch/arm/configs/h3600_defconfig | 1 - arch/arm/configs/hisi_defconfig | 1 - arch/arm/configs/imx_v4_v5_defconfig | 1 - arch/arm/configs/integrator_defconfig | 1 - arch/arm/configs/ixp4xx_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 1 - arch/arm/configs/keystone_defconfig | 1 - arch/arm/configs/lpc32xx_defconfig | 1 - arch/arm/configs/mmp2_defconfig | 1 - arch/arm/configs/moxart_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 1 - arch/arm/configs/multi_v5_defconfig | 1 - arch/arm/configs/mv78xx0_defconfig | 2 -- arch/arm/configs/mvebu_v5_defconfig | 1 - arch/arm/configs/mxs_defconfig | 1 - arch/arm/configs/neponset_defconfig | 1 + arch/arm/configs/netwinder_defconfig | 1 + arch/arm/configs/nhk8815_defconfig | 1 - arch/arm/configs/omap1_defconfig | 2 -- arch/arm/configs/orion5x_defconfig | 2 -- arch/arm/configs/pxa168_defconfig | 2 -- arch/arm/configs/pxa3xx_defconfig | 2 -- arch/arm/configs/pxa910_defconfig | 2 -- arch/arm/configs/pxa_defconfig | 1 - arch/arm/configs/rpc_defconfig | 1 + arch/arm/configs/spear13xx_defconfig | 1 - arch/arm/configs/spitz_defconfig | 1 - arch/arm/configs/versatile_defconfig | 1 - arch/arm/configs/vt8500_v6_v7_defconfig | 1 - arch/arm/configs/wpcm450_defconfig | 1 - 44 files changed, 11 insertions(+), 53 deletions(-)arch/arm/Kconfig +6
-9@@ -1153,17 +1153,14 @@ config ARM_PATCH_IDIV config AEABI bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \ !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG - default CPU_V7 || CPU_V7M || CPU_V6 || CPU_V6K || CC_IS_CLANG + default y help - This option allows for the kernel to be compiled using the latest - ARM ABI (aka EABI). This is only useful if you are using a user - space environment that is also compiled with EABI. + The Arm EABI is the default ABI on all modern Linux + distributions, replacing the obsolete and "OABI" that was + commonly used on ARMv4 distributions before ca. 2013. - Since there are major incompatibilities between the legacy ABI and - EABI, especially with regard to structure member alignment, this - option also changes the kernel syscall calling convention to - disambiguate both ABIs and allow for backward compatibility support - (selected with CONFIG_OABI_COMPAT). + Everyone should enable this, as support for OABI user space + was dropped in gcc-4.8 and most distributions after ca. 2013. config OABI_COMPAT bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"arch/arm/configs/am200epdkit_defconfig +0
-1@@ -7,7 +7,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y -CONFIG_AEABI=y # CONFIG_OABI_COMPAT is not set CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=yarch/arm/configs/aspeed_g4_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_ASPEED=y CONFIG_MACH_ASPEED_G4=y CONFIG_VMSPLIT_2G=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_JUMP_LABEL=yarch/arm/configs/assabet_defconfig +1
-0@@ -5,6 +5,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y +# CONFIG_AEABI is not set CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram" CONFIG_FPE_NWFPE=y CONFIG_PM=yarch/arm/configs/at91_dt_defconfig +0
-1@@ -18,7 +18,6 @@ CONFIG_SOC_AT91SAM9=y CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/axm55xx_defconfig +0
-1@@ -38,7 +38,6 @@ CONFIG_PCIE_AXXIA=y CONFIG_SMP=y CONFIG_NR_CPUS=16 CONFIG_HOTPLUG_CPU=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/bcm2835_defconfig +0
-1@@ -25,7 +25,6 @@ CONFIG_CRASH_DUMP=y CONFIG_ARCH_MULTI_V6=y CONFIG_ARCH_BCM=y CONFIG_ARCH_BCM2835=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_KEXEC=y CONFIG_CPU_FREQ=yarch/arm/configs/clps711x_defconfig +0
-1@@ -6,7 +6,6 @@ CONFIG_RD_LZMA=y CONFIG_EXPERT=y CONFIG_JUMP_LABEL=y CONFIG_PARTITION_ADVANCED=y -CONFIG_AEABI=y # CONFIG_COREDUMP is not set CONFIG_SLUB_TINY=y CONFIG_NET=yarch/arm/configs/collie_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_COLLIE=y CONFIG_CMDLINE="noinitrd root=/dev/mtdblock2 rootfstype=jffs2 fbcon=rotate:1" -CONFIG_FPE_NWFPE=y CONFIG_PM=y # CONFIG_SWAP is not set CONFIG_SLUB_TINY=yarch/arm/configs/davinci_all_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_ARCH_DAVINCI=y CONFIG_ARCH_DAVINCI_DA850=y CONFIG_DAVINCI_MUX_DEBUG=y CONFIG_DAVINCI_MUX_WARNINGS=y -CONFIG_AEABI=y CONFIG_SECCOMP=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/dove_defconfig +0
-1@@ -7,7 +7,6 @@ CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_DOVE=y CONFIG_MACH_CM_A510=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/ep93xx_defconfig +0
-1@@ -18,7 +18,6 @@ CONFIG_MACH_EDB9315=y CONFIG_MACH_EDB9315A=y CONFIG_MACH_TS72XX=y CONFIG_MACH_VISION_EP9307=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyAM0,115200 root=/dev/nfs ip=bootp" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/footbridge_defconfig +1
-0@@ -11,6 +11,7 @@ CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=yarch/arm/configs/gemini_defconfig +0
-1@@ -11,7 +11,6 @@ CONFIG_KEXEC=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_GEMINI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_CMDLINE="console=ttyS0,115200n8" CONFIG_PM=yarch/arm/configs/h3600_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_H3600=y # CONFIG_CPU_FREQ_STAT is not set -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_UNIX=yarch/arm/configs/hisi_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_ARCH_HIP04=y CONFIG_ARCH_HIX5HD2=y CONFIG_SMP=y CONFIG_NR_CPUS=16 -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/imx_v4_v5_defconfig +0
-1@@ -15,7 +15,6 @@ CONFIG_ARCH_MXC=y CONFIG_SOC_IMX1=y CONFIG_SOC_IMX25=y CONFIG_SOC_IMX27=y -CONFIG_AEABI=y CONFIG_PM_DEBUG=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/integrator_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_ARCH_INTEGRATOR=y CONFIG_ARCH_INTEGRATOR_AP=y CONFIG_INTEGRATOR_IMPD1=y CONFIG_ARCH_INTEGRATOR_CP=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyAM0,38400n8 root=/dev/nfs ip=bootp" CONFIG_CPU_FREQ=yarch/arm/configs/ixp4xx_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_IXP4XX=y CONFIG_CPU_BIG_ENDIAN=y -CONFIG_AEABI=y CONFIG_CMDLINE="console=ttyS0,115200" CONFIG_STRICT_KERNEL_RWX=y CONFIG_STRICT_MODULE_RWX=yarch/arm/configs/jornada720_defconfig +0
-1@@ -5,7 +5,6 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_SA1100=y CONFIG_SA1100_JORNADA720=y CONFIG_SA1100_JORNADA720_SSP=y -CONFIG_FPE_NWFPE=y CONFIG_PM=y CONFIG_MODULES=y CONFIG_NET=yarch/arm/configs/keystone_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_PCI_KEYSTONE=y CONFIG_SMP=y CONFIG_HOTPLUG_CPU=y CONFIG_ARM_PSCI=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_VFP=y CONFIG_NEON=yarch/arm/configs/lpc32xx_defconfig +0
-1@@ -10,7 +10,6 @@ CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_LPC32XX=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CMDLINE="console=ttyS0,115200n81 root=/dev/ram0"arch/arm/configs/mmp2_defconfig +0
-1@@ -4,7 +4,6 @@ CONFIG_PREEMPT=y CONFIG_LOG_BUF_SHIFT=14 # CONFIG_BLK_DEV_BSG is not set CONFIG_ARCH_MMP=y -CONFIG_AEABI=y CONFIG_MACH_MMP2_DT=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS2,38400 mem=128M user_debug=255 earlyprintk" CONFIG_VFP=yarch/arm/configs/moxart_defconfig +0
-1@@ -16,7 +16,6 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MOXART=y CONFIG_MACH_UC7112LX=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y # CONFIG_SWAP is not setarch/arm/configs/multi_v4t_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_INTEGRATOR_IMPD1=y CONFIG_INTEGRATOR_CM720T=y CONFIG_INTEGRATOR_CM920T=y CONFIG_INTEGRATOR_CM922T_XA10=y -CONFIG_AEABI=y # CONFIG_ATAGS is not set CONFIG_CPU_IDLE=y CONFIG_ARM_CPUIDLE=yarch/arm/configs/multi_v5_defconfig +0
-1@@ -36,7 +36,6 @@ CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/mv78xx0_defconfig +0
-2@@ -11,9 +11,7 @@ CONFIG_ARCH_MULTI_V5=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MV78XX0=y CONFIG_MACH_TERASTATION_WXL=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/mvebu_v5_defconfig +0
-1@@ -22,7 +22,6 @@ CONFIG_MACH_MV2120=y CONFIG_MACH_D2NET_DT=y CONFIG_MACH_NET2BIG=y CONFIG_MACH_MSS2_DT=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=yarch/arm/configs/mxs_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_PERF_EVENTS=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MXS=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/neponset_defconfig +1
-0@@ -11,6 +11,7 @@ CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=y CONFIG_CMDLINE="console=ttySA0,38400n8 cpufreq=221200 rw root=/dev/mtdblock2 mtdparts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) mem=32M noinitrd initrd=0xc0800000,3M" CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_PM=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/netwinder_defconfig +1
-0@@ -4,6 +4,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_NETWINDER=y +# CONFIG_AEABI is not set CONFIG_DEPRECATED_PARAM_STRUCT=y CONFIG_CMDLINE="root=0x801" CONFIG_FPE_NWFPE=yarch/arm/configs/nhk8815_defconfig +0
-1@@ -12,7 +12,6 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_NOMADIK=y CONFIG_MACH_NOMADIK_8815NHK=y -CONFIG_AEABI=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_SWAP is not setarch/arm/configs/omap1_defconfig +0
-2@@ -28,9 +28,7 @@ CONFIG_MACH_OMAP_PALMTE=y CONFIG_MACH_SX1=y CONFIG_MACH_NOKIA770=y CONFIG_MACH_AMS_DELTA=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=1f03 rootfstype=jffs2" -CONFIG_FPE_NWFPE=y # CONFIG_SUSPEND is not set CONFIG_PM=y CONFIG_MODULES=yarch/arm/configs/orion5x_defconfig +0
-2@@ -20,10 +20,8 @@ CONFIG_MACH_TS409=y CONFIG_MACH_TS78XX=y CONFIG_MACH_MV2120=y CONFIG_MACH_NET2BIG=y -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y -CONFIG_FPE_NWFPE=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/pxa168_defconfig +0
-2@@ -3,11 +3,9 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ_IDLE=y CONFIG_HIGH_RES_TIMERS=y CONFIG_PREEMPT=y -CONFIG_AEABI=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_ARCH_MMP=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.2.100:/nfsroot/ ip=192.168.2.101:192.168.2.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=128M" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=yarch/arm/configs/pxa3xx_defconfig +0
-2@@ -7,9 +7,7 @@ CONFIG_KALLSYMS_ALL=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_MACH_PXA3XX_DT=y -CONFIG_AEABI=y CONFIG_CMDLINE="root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on console=ttyS0,115200 mem=64M debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_PACKET=yarch/arm/configs/pxa910_defconfig +0
-2@@ -10,8 +10,6 @@ CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_BLK_DEV_BSG is not set -CONFIG_AEABI=y -CONFIG_FPE_NWFPE=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=yarch/arm/configs/pxa_defconfig +0
-1@@ -20,7 +20,6 @@ CONFIG_ARCH_GUMSTIX=y CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y -CONFIG_AEABI=y CONFIG_ARCH_FORCE_MAX_ORDER=8 CONFIG_CMDLINE="root=/dev/ram0 ro" CONFIG_CPU_FREQ=yarch/arm/configs/rpc_defconfig +1
-0@@ -7,6 +7,7 @@ CONFIG_ARCH_MULTI_V4=y CONFIG_ARCH_RPC=y CONFIG_CPU_SA110=y CONFIG_FPE_NWFPE=y +# CONFIG_AEABI is not set CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=yarch/arm/configs/spear13xx_defconfig +0
-1@@ -9,7 +9,6 @@ CONFIG_MACH_SPEAR1340=y CONFIG_SMP=y # CONFIG_SMP_ON_UP is not set # CONFIG_ARM_CPU_TOPOLOGY is not set -CONFIG_AEABI=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=yarch/arm/configs/spitz_defconfig +0
-1@@ -11,7 +11,6 @@ CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/mtdblock2 rootfstype=jffs2 debug" -CONFIG_FPE_NWFPE=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=yarch/arm/configs/versatile_defconfig +0
-1@@ -6,7 +6,6 @@ CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_VERSATILE=y -CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_CMDLINE="root=1f03 mem=32M" CONFIG_FPE_NWFPE=yarch/arm/configs/vt8500_v6_v7_defconfig +0
-1@@ -8,7 +8,6 @@ CONFIG_ARM_ERRATA_720789=y CONFIG_ARM_ERRATA_754322=y CONFIG_ARM_ERRATA_775420=y CONFIG_HAVE_ARM_ARCH_TIMER=y -CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y CONFIG_ARM_APPENDED_DTB=yarch/arm/configs/wpcm450_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_PROFILING=y CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_CPU_DCACHE_WRITETHROUGH=y -CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=ySignature · 1 line
2.39.5
Re: [PATCH v2 03/19] ARM: rework ARM11 CPU selection logic
In reply to Arnd BergmannQuoted 42 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Support for SMP on ARM1136r0 has been broken for a while, and nobody is working on fixing it. I had a plan to change ARMv6 support to no longer coexist in a common kernel with ARMv7 CPUs but instead ARMv5 and below. This would have addressed the problem, but after a recent mailing list discussion, we concluded that an easier approach is to just forbid ARM1136r0 CPU support on SMP-enabled kernels.
This mainly affects users of the Nokia N800/N810 tablets using an OMAP2420 SoC, which is the only commercial product with an ARM1136r0 that is still supported by the kernel.
The other machines that are still in the same hardware catogory are:
- TI OMAP2420 H4 reference board
- TI OMAP2430 SDP software development platform
- Freescale/NXP i.MX31 Lite Development Kit
- Buglabs i.MX31 Bug 1.x prototype
- Arm Integrator/AP with CM1136JF-S core moduleTo my knowledge, none of these have any actual users aside from reference boards being used more easily test the platforms.
There are also a few ARM1136r1 machines, which implement the ARMv6K SMP support (barriers, atomics and TLS):
- Eukrea CPUIMX35 reference platform
- Freescale/NXP i.MX35 Product Development Kit
- ARM Integrator/CP/IM-LT3 with ARM1136J Core Tile
- ARM Realview/EB with ARM1136J Core TileAgain, these are mainly reference implementations rather than actual products, but since they support ARMv6K, they should continue to work correctly in SMP-enabled kernels. For the ARM Core Tile, I have not found a datasheet but instead use the revision based on what the respective virtual models report.
All the other ARMv6 platforms use an ARM1176 with ARMv6K, VMSAv7 and Trustzone support.
Quoted 7 lines
To avoid the broken configuration, annotate the ARM1136 based machines with specific
CPU_ARM1136R0orCPU_ARM1136R2symbols inKconfigand make the r0 variants depend on !SMP.
Quoted 154 lines
--- arch/arm/Kconfig.platforms | 2 +- arch/arm/mach-imx/Kconfig | 4 +++- arch/arm/mach-omap2/Kconfig | 3 ++- arch/arm/mach-versatile/Kconfig | 10 +++++----- arch/arm/mm/Kconfig | 24 +++++++++++++++++++++++- 5 files changed, 34 insertions(+), 9 deletions(-)arch/arm/Kconfig.platforms +1
-1@@ -33,7 +33,7 @@ config ARCH_MULTI_V4_V5 config ARCH_MULTI_V6 bool "ARMv6 based platforms (ARM11)" select ARCH_MULTI_V6_V7 - select CPU_V6K + select CPU_ARM1176 config ARCH_MULTI_V7 bool "ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)"arch/arm/mach-imx/Kconfig +3
-1@@ -41,13 +41,15 @@ comment "ARM1136 platforms" config SOC_IMX31 bool "i.MX31 support" - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor config SOC_IMX35 bool "i.MX35 support" + select CPU_ARM1136R1 select MXC_AVIC help This enables support for Freescale i.MX35 processorarch/arm/mach-omap2/Kconfig +2
-1@@ -8,8 +8,9 @@ config OMAP_HWMOD config ARCH_OMAP2 bool "TI OMAP2" depends on ARCH_MULTI_V6 + depends on !SMP select ARCH_OMAP2PLUS - select CPU_V6 + select CPU_ARM1136R0 select OMAP_HWMOD select SOC_HAS_OMAP2_SDRCarch/arm/mach-versatile/Kconfig +5
-5@@ -113,7 +113,8 @@ config INTEGRATOR_CM1136JFS bool "Integrator/CM1136JF-S core module" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 - select CPU_V6 + depends on !SMP + select CPU_ARM1136R0 config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"@@ -135,7 +136,7 @@ config INTEGRATOR_CTB36 bool "Integrator/CTB36 (ARM1136JF-S) core tile" depends on ARCH_INTEGRATOR_CP depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 config ARCH_CINTEGRATOR depends on ARCH_INTEGRATOR_CP@@ -182,7 +183,7 @@ config MACH_REALVIEW_EB config REALVIEW_EB_ARM1136 bool "Support ARM1136J(F)-S Tile" depends on MACH_REALVIEW_EB && ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1136R1 help Enable support for the ARM1136 tile fitted to the Realview(R) Emulation Baseboard platform.@@ -201,11 +202,10 @@ config REALVIEW_EB_A9MP Enable support for the Cortex-A9MPCore tile fitted to the Realview(R) Emulation Baseboard platform. -# ARMv6 CPU without K extensions, but does have the new exclusive ops config MACH_REALVIEW_PB1176 bool "Support RealView(R) Platform Baseboard for ARM1176JZF-S" depends on ARCH_MULTI_V6 - select CPU_V6 + select CPU_ARM1176 select HAVE_TCM help Include support for the ARM(R) RealView(R) Platform Baseboard forarch/arm/mm/Kconfig +23
-1@@ -376,6 +376,7 @@ config CPU_PJ4B # ARMv6 config CPU_V6 bool + depends on !SMP select CPU_32v6 select CPU_ABRT_EV6 select CPU_CACHE_V6@@ -386,7 +387,6 @@ config CPU_V6 select CPU_PABRT_V6 select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU - select SMP_ON_UP if SMP # ARMv6k config CPU_V6K@@ -403,6 +403,28 @@ config CPU_V6K select CPU_THUMB_CAPABLE select CPU_TLB_V6 if MMU +config CPU_ARM1136R0 + bool + select CPU_V6 + depends on !SMP + help + These early revisions of ARM1136 lack support for the + ARMv6k extensions for multiprocessing. + +config CPU_ARM1136R1 + bool + select CPU_V6K + help + Later revisions of ARM1136 add ARMv6k (atomics, barriers + and TLS register) in addition to the features from r0. + +config CPU_ARM1176 + bool + select CPU_V6K + help + ARM1176 implements ARMv6k, VMSAv7 and Trustzone in + addition to the ARMv6 baseline. + # ARMv7 and ARMv8 architectures config CPU_V7 boolSignature · 1 line
2.39.5
Re: [PATCH v2 04/19] ARM: deprecate support for ARM1136r0
In reply to Arnd BergmannHi,
Quoted 9 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
This CPU revision remains a special case as it is now incompatible with
CONFIG_SMP. Only the Nokia N8x0 is used in practice, and even that one is fairly rare these days, so let's plan to remove all of them after the 2026 LTS kernel release.Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
A.
Quoted 112 lines
--- arch/arm/mach-imx/Kconfig | 5 ++++- arch/arm/mach-omap2/Kconfig | 15 ++++++++++++--- arch/arm/mach-versatile/Kconfig | 5 ++++- arch/arm/mm/Kconfig | 2 ++ 4 files changed, 22 insertions(+), 5 deletions(-)arch/arm/mach-imx/Kconfig +4
-1@@ -40,13 +40,16 @@ if ARCH_MULTI_V6 comment "ARM1136 platforms" config SOC_IMX31 - bool "i.MX31 support" + bool "i.MX31 support (DEPRECATED)" depends on !SMP select CPU_ARM1136R0 select MXC_AVIC help This enables support for Freescale i.MX31 processor + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. + config SOC_IMX35 bool "i.MX35 support" select CPU_ARM1136R1arch/arm/mach-omap2/Kconfig +12
-3@@ -207,18 +207,24 @@ comment "OMAP Core Type" depends on ARCH_OMAP2 config SOC_OMAP2420 - bool "OMAP2420 support" + bool "OMAP2420 support (DEPRECATED)" depends on ARCH_OMAP2 default y select OMAP_DM_SYSTIMER select OMAP_DM_TIMER select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP2430 - bool "OMAP2430 support" + bool "OMAP2430 support (DEPRECATED)" depends on ARCH_OMAP2 default y select SOC_HAS_OMAP2_SDRC + help + This SoC is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config SOC_OMAP3430 bool "OMAP3430 support"@@ -249,11 +255,14 @@ config MACH_NOKIA_N810_WIMAX bool config MACH_NOKIA_N8X0 - bool "Nokia N800/N810" + bool "Nokia N800/N810 (DEPRECATED)" depends on SOC_OMAP2420 default y select MACH_NOKIA_N810 select MACH_NOKIA_N810_WIMAX + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. endmenuarch/arm/mach-versatile/Kconfig +4
-1@@ -110,11 +110,14 @@ config INTEGRATOR_CM1026EJS select CPU_ARM1026 config INTEGRATOR_CM1136JFS - bool "Integrator/CM1136JF-S core module" + bool "Integrator/CM1136JF-S core module (DEPRECATED)" depends on ARCH_INTEGRATOR_AP depends on ARCH_MULTI_V6 depends on !SMP select CPU_ARM1136R0 + help + This machine is scheduled for removal in early 2027, + since it uses the ARM1136r0 CPU revision. config ARCH_INTEGRATOR_CP bool "Support Integrator/CP platform"arch/arm/mm/Kconfig +2
-0@@ -410,6 +410,8 @@ config CPU_ARM1136R0 help These early revisions of ARM1136 lack support for the ARMv6k extensions for multiprocessing. + Support for this revision is scheduled for removal + from the kernel in early 2027. config CPU_ARM1136R1 boolSignature · 1 line
2.39.5
Re: [PATCH v2 05/19] ARM: turn CONFIG_ATAGS off by default
In reply to Arnd BergmannHi,
Quoted 16 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Only a very small number of machines remain that rely on traditional board files with the ATAGS boot data instead of devicetree, and we have not accepted new ones for a decade.
Most of the remaining ones are on their way out of the kernel, but the
Kconfigoption that controls ATAGS is still enabled by default.To reflect the actual status of ATAGS support and alert the remaining users of upstream and out-of-tree platforms with this, chanyge it to being default-disabled and add a dependency on
CONFIG_EXPERT.
Quoted 7 lines
The board specific defconfig files that rely on ATAGS are changed to turn on both EXPERT and ATAGS if they were not doing thath already, and the ones that explicitly turned it off before no longer need to.
Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
A.
Quoted 399 lines
--- arch/arm/Kconfig | 13 ++++++++----- arch/arm/configs/am200epdkit_defconfig | 1 + arch/arm/configs/aspeed_g4_defconfig | 1 - arch/arm/configs/aspeed_g5_defconfig | 1 - arch/arm/configs/assabet_defconfig | 2 ++ arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/collie_defconfig | 1 + arch/arm/configs/dove_defconfig | 1 + arch/arm/configs/footbridge_defconfig | 1 + arch/arm/configs/h3600_defconfig | 2 ++ arch/arm/configs/integrator_defconfig | 1 - arch/arm/configs/jornada720_defconfig | 2 ++ arch/arm/configs/moxart_defconfig | 1 - arch/arm/configs/mps2_defconfig | 1 - arch/arm/configs/multi_v4t_defconfig | 1 - arch/arm/configs/mv78xx0_defconfig | 1 + arch/arm/configs/neponset_defconfig | 2 ++ arch/arm/configs/netwinder_defconfig | 2 ++ arch/arm/configs/omap1_defconfig | 1 + arch/arm/configs/rpc_defconfig | 2 ++ arch/arm/configs/s3c6400_defconfig | 2 ++ arch/arm/configs/sama5_defconfig | 1 - arch/arm/configs/sama7_defconfig | 1 - arch/arm/configs/spitz_defconfig | 1 + arch/arm/configs/stm32_defconfig | 3 ++- arch/arm/configs/wpcm450_defconfig | 1 - 26 files changed, 31 insertions(+), 16 deletions(-)arch/arm/Kconfig +8
-5@@ -1390,12 +1390,15 @@ config ARCH_WANT_FLAT_DTB_INSTALL config ATAGS bool "Support for the traditional ATAGS boot data passing" - default y + depends on EXPERT help - This is the traditional way of passing data to the kernel at boot - time. If you are solely relying on the flattened device tree (or - the ARM_ATAG_DTB_COMPAT option) then you may unselect this option - to remove ATAGS support from your kernel binary. + This is the traditional way of passing data to the kernel at + boot but is now only used by a few of the oldest ARMv4 and + ARMv5 machines. Users that still rely on ATAGS should plan + on migrating to devicetree based booting. + + Support for ATAGS will be removed when the last machine using + it is either converted to DT or removed. config DEPRECATED_PARAM_STRUCT bool "Provide old way to pass kernel parameters"arch/arm/configs/am200epdkit_defconfig +1
-0@@ -7,6 +7,7 @@ CONFIG_EXPERT=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_PXA=y CONFIG_ARCH_GUMSTIX=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/aspeed_g4_defconfig +0
-1@@ -23,7 +23,6 @@ CONFIG_ARCH_ASPEED=y CONFIG_MACH_ASPEED_G4=y CONFIG_VMSPLIT_2G=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_JUMP_LABEL=y CONFIG_STRICT_KERNEL_RWX=y # CONFIG_BLK_DEBUG_FS is not setarch/arm/configs/aspeed_g5_defconfig +0
-1@@ -29,7 +29,6 @@ CONFIG_VMSPLIT_2G=y CONFIG_NR_CPUS=2 CONFIG_HIGHMEM=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_VFP=y CONFIG_NEON=y CONFIG_KERNEL_MODE_NEON=yarch/arm/configs/assabet_defconfig +2
-0@@ -1,11 +1,13 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram" CONFIG_FPE_NWFPE=y CONFIG_PM=yarch/arm/configs/at91_dt_defconfig +0
-1@@ -19,7 +19,6 @@ CONFIG_SOC_SAM9X60=y CONFIG_SOC_SAM9X7=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw"arch/arm/configs/collie_defconfig +1
-0@@ -9,6 +9,7 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_COLLIE=y +CONFIG_ATAGS=y CONFIG_CMDLINE="noinitrd root=/dev/mtdblock2 rootfstype=jffs2 fbcon=rotate:1" CONFIG_PM=y # CONFIG_SWAP is not setarch/arm/configs/dove_defconfig +1
-0@@ -8,6 +8,7 @@ CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_DOVE=y CONFIG_MACH_CM_A510=y CONFIG_HIGHMEM=y +CONFIG_ATAGS=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_VFP=yarch/arm/configs/footbridge_defconfig +1
-0@@ -10,6 +10,7 @@ CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_EBSA285_HOST=y CONFIG_ARCH_NETWINDER=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_FPE_NWFPE=y CONFIG_FPE_NWFPE_XP=y CONFIG_MODULES=yarch/arm/configs/h3600_defconfig +2
-0@@ -4,11 +4,13 @@ CONFIG_HIGH_RES_TIMERS=y CONFIG_PREEMPT=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_H3600=y # CONFIG_CPU_FREQ_STAT is not set +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_UNIX=yarch/arm/configs/integrator_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_ARCH_INTEGRATOR=y CONFIG_ARCH_INTEGRATOR_AP=y CONFIG_INTEGRATOR_IMPD1=y CONFIG_ARCH_INTEGRATOR_CP=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyAM0,38400n8 root=/dev/nfs ip=bootp" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_POWERSAVE=yarch/arm/configs/jornada720_defconfig +2
-0@@ -1,11 +1,13 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_JORNADA720=y CONFIG_SA1100_JORNADA720_SSP=y CONFIG_PM=y +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_NET=y CONFIG_PACKET=yarch/arm/configs/moxart_defconfig +0
-1@@ -16,7 +16,6 @@ CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_MOXART=y CONFIG_MACH_UC7112LX=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y # CONFIG_SWAP is not set # CONFIG_COMPAT_BRK is not setarch/arm/configs/mps2_defconfig +0
-1@@ -16,7 +16,6 @@ CONFIG_ARCH_MPS2=y CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x21000000 CONFIG_DRAM_SIZE=0x1000000 -# CONFIG_ATAGS is not set # CONFIG_SUSPEND is not set # CONFIG_BLOCK is not set CONFIG_BINFMT_FLAT=yarch/arm/configs/multi_v4t_defconfig +0
-1@@ -17,7 +17,6 @@ CONFIG_INTEGRATOR_IMPD1=y CONFIG_INTEGRATOR_CM720T=y CONFIG_INTEGRATOR_CM920T=y CONFIG_INTEGRATOR_CM922T_XA10=y -# CONFIG_ATAGS is not set CONFIG_CPU_IDLE=y CONFIG_ARM_CPUIDLE=y CONFIG_ARM_CLPS711X_CPUIDLE=yarch/arm/configs/mv78xx0_defconfig +1
-0@@ -12,6 +12,7 @@ CONFIG_ARCH_MULTI_V5=y CONFIG_ARCH_MV78XX0=y CONFIG_MACH_TERASTATION_WXL=y CONFIG_HIGHMEM=y +CONFIG_ATAGS=y CONFIG_VFP=y CONFIG_KPROBES=y CONFIG_MODULES=yarch/arm/configs/neponset_defconfig +2
-0@@ -1,12 +1,14 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_SA1100=y CONFIG_SA1100_ASSABET=y CONFIG_ASSABET_NEPONSET=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_ZBOOT_ROM_TEXT=0x80000 CONFIG_ZBOOT_ROM_BSS=0xc1000000 CONFIG_ZBOOT_ROM=yarch/arm/configs/netwinder_defconfig +2
-0@@ -1,10 +1,12 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_FOOTBRIDGE=y CONFIG_ARCH_NETWINDER=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_DEPRECATED_PARAM_STRUCT=y CONFIG_CMDLINE="root=0x801" CONFIG_FPE_NWFPE=yarch/arm/configs/omap1_defconfig +1
-0@@ -28,6 +28,7 @@ CONFIG_MACH_OMAP_PALMTE=y CONFIG_MACH_SX1=y CONFIG_MACH_NOKIA770=y CONFIG_MACH_AMS_DELTA=y +CONFIG_ATAGS=y CONFIG_CMDLINE="root=1f03 rootfstype=jffs2" # CONFIG_SUSPEND is not set CONFIG_PM=yarch/arm/configs/rpc_defconfig +2
-0@@ -2,12 +2,14 @@ CONFIG_SYSVIPC=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y +CONFIG_EXPERT=y CONFIG_ARCH_MULTI_V4=y # CONFIG_ARCH_MULTI_V7 is not set CONFIG_ARCH_RPC=y CONFIG_CPU_SA110=y CONFIG_FPE_NWFPE=y # CONFIG_AEABI is not set +CONFIG_ATAGS=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=yarch/arm/configs/s3c6400_defconfig +2
-0@@ -2,8 +2,10 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_KALLSYMS_ALL=y CONFIG_ARCH_MULTI_V6=y # CONFIG_ARCH_MULTI_V7 is not set +CONFIG_EXPERT=y CONFIG_ARCH_S3C64XX=y CONFIG_MACH_WLF_CRAGG_6410=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttySAC0,115200 root=/dev/ram init=/linuxrc initrd=0x51000000,6M ramdisk_size=6144" CONFIG_VFP=y CONFIG_MODULES=yarch/arm/configs/sama5_defconfig +0
-1@@ -13,7 +13,6 @@ CONFIG_SOC_SAMA5D3=y CONFIG_SOC_SAMA5D4=y # CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw" CONFIG_VFP=y CONFIG_NEON=yarch/arm/configs/sama7_defconfig +0
-1@@ -20,7 +20,6 @@ CONFIG_ATMEL_CLOCKSOURCE_TCB=y # CONFIG_CPU_SW_DOMAIN_PAN is not set CONFIG_ARCH_FORCE_MAX_ORDER=14 CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_CMDLINE="console=ttyS0,115200 earlyprintk ignore_loglevel" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE=yarch/arm/configs/spitz_defconfig +1
-0@@ -10,6 +10,7 @@ CONFIG_ARCH_PXA=y CONFIG_PXA_SHARPSL=y CONFIG_MACH_AKITA=y CONFIG_MACH_BORZOI=y +CONFIG_ATAGS=y CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/mtdblock2 rootfstype=jffs2 debug" CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=yarch/arm/configs/stm32_defconfig +2
-1@@ -20,7 +20,8 @@ CONFIG_ARCH_STM32=y CONFIG_CPU_V7M_NUM_IRQ=240 CONFIG_SET_MEM_PARAM=y CONFIG_DRAM_BASE=0x90000000 -# CONFIG_ATAGS is not set +CONFIG_FLASH_MEM_BASE=0x08000000 +CONFIG_FLASH_SIZE=0x00200000 CONFIG_XIP_KERNEL=y CONFIG_XIP_PHYS_ADDR=0x08008000 # CONFIG_SUSPEND is not setarch/arm/configs/wpcm450_defconfig +0
-1@@ -14,7 +14,6 @@ CONFIG_ARCH_NPCM=y CONFIG_ARCH_WPCM450=y CONFIG_CPU_DCACHE_WRITETHROUGH=y CONFIG_UACCESS_WITH_MEMCPY=y -# CONFIG_ATAGS is not set CONFIG_ARM_APPENDED_DTB=y CONFIG_CPU_IDLE=y CONFIG_KPROBES=ySignature · 1 line
2.39.5
Linus Walleij
maintainerRe: [PATCH v2 14/19] ARM: mark mach-sa1100 as deprecated
In reply to Arnd BergmannQuoted 7 lines · Arnd Bergmann
If anyone is still running one of these four machines and planning to keep updating their kernels, please speak up now so we can adapt the plans as needed.
If nobody is found using StrongARM1100 any more, it can be removing during 2027, leaving 6.12-LTS as the last longterm support kernel for it.
I thought for a while I would do it but didn't have the time or energy, so I dropped the ball on this.
That said, the current LLM code agents are a bliss for tedious tasks like this, it should be pretty straight-forward to convert SA1100 to DT-only if (and only if) there is active interest.
Yours,
Linus Walleij
Re: [PATCH v2 14/19] ARM: mark mach-sa1100 as deprecated
Quoted 10 lines · Linus Walleij
Quoted 7 lines · Arnd Bergmann
If anyone is still running one of these four machines and planning to keep updating their kernels, please speak up now so we can adapt the plans as needed.
If nobody is found using StrongARM1100 any more, it can be removing during 2027, leaving 6.12-LTS as the last longterm support kernel for it.
Quoted 6 lines
I thought for a while I would do it but didn't have the time or energy, so I dropped the ball on this.
That said, the current LLM code agents are a bliss for tedious tasks like this, it should be pretty straight-forward to convert SA1100 to DT-only if (and only if) there is active interest.
Right, and of course we can always bring it back later if we someone does a DT port, we would just treat it as a new platform then. I had started cleaning up arch/arm/mach-sa1100/include/mach/ at some point in the past but gave up as it got too hard to untangle those without breaking stuff. A new port would likely be easier there.
Arnd
Re: [PATCH v2 19/19] ARM: mark mv78xx0 support as deprecated
In reply to Arnd BergmannQuoted 10 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Only one machine remains supported and was kept in 2022 for the
Debian_on_Buffaloproject that was still using this, with plans to convert it to devicetree.The conversion never happened, and
Debian_on_Buffalodoes not provide kernels later than linux-6.1, so it is unlikely to still be useful for a DT conversion in the future.
Quoted 5 lines
Mark the platform for deprecation after the next LTS kernel, which should give any remaining users a few more years of bugfixes.
Thanks,
Gregory
Quoted 28 lines
--- arch/arm/mach-mv78xx0/Kconfig | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)arch/arm/mach-mv78xx0/Kconfig +3
-1@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only menuconfig ARCH_MV78XX0 - bool "Marvell MV78xx0" + bool "Marvell MV78xx0 (DEPRECATED)" depends on ARCH_MULTI_V5 depends on CPU_LITTLE_ENDIAN depends on ATAGS@@ -14,6 +14,8 @@ menuconfig ARCH_MV78XX0 Support for the following Marvell MV78xx0 series SoCs: MV781x0, MV782x0. + This platform is scheduled for removal in early 2027. + if ARCH_MV78XX0 config MACH_TERASTATION_WXLSignature · 1 line
2.39.5
Signature · 3 lines
Grégory CLEMENT, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [PATCH v2 18/19] ARM: mark axxia platform as deprecated
In reply to Arnd BergmannQuoted 13 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
The Axxia platform was initially upstream by Anders Berg for LSI and later Avago, but this included only support for I2C and reset drivers, while most of the interesting bits (network, pci, rapidio, usb, ...) or the arm64 platform support were never merged.
The downstream kernel was maintained by Intel up to linux-5.15 when the product line was discontinued. Known users include Nokia and Ericsson, but both of them use kernels derived from the out-of-tree drivers rather than the upstream version, and will be able to continue doing that even when the rudimentary mainline support is gone.
Quoted 6 lines
Mark it as deprecated for removal after the next LTS kernel.
Cc Stefan Wiehler <[email protected]>Cc Alexander Sverdlin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
Quoted 22 lines
---
arch/arm/mach-axxia/Kconfig | 4 +++-1 file changed, 3 insertions(+), 1 deletion(-)arch/arm/mach-axxia/Kconfig +0
-0@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0config
ARCH_AXXIAarch/arm/mach-axxia/Kconfig +1
-1- bool "LSI Axxia platforms" + bool "LSI Axxia platforms (DEPRECATED)"depends on
ARCH_MULTI_V7&&ARM_LPAE
selectARM_AMBA
selectARM_GICarch/arm/mach-axxia/Kconfig +0
-0@@ -13,3 +13,5 @@ config ARCH_AXXIA
The LSI Axxia platforms require a Flattened Device Tree to be passed to the kernel.arch/arm/mach-axxia/Kconfig +2
-0+ + This platform is scheduled for removal in early 2027
Signature · 3 lines
Alexander Sverdlin Siemens AG www.siemens.com
Re: [PATCH v2 01/19] ARM: use CONFIG_AEABI by default everywhere
In reply to Arnd BergmannHi Arnd,
Quoted 19 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
On ARMv4 and ARMv5, the default is still to build for OABI, with
CONFIG_AEABIdisabled, even though distros and toolchains no longer support OABI as a target.Change the default to EABI for all architecture levels and change the defconfig entries as follows:
- All machines that used to explicitly enable EABI can drop that line now
- Machines that are likely to actually use old distros and had NWFPE enabled in combination with OABI (rpc, footrbridge, netwinder, assabet, neponset) explicitly turn it on now.
- Machines that already had both EABI and NWFPE disabled in defconfig (at91_dt, collie, ep93xx, gemini, h3600,imx_v4_v5, integrator, jornada, moxart,multi_v4t, omap1) were likely not usable with either OABI or EABI and now use EABI instead implicitly, making it more likely that they could work.
Quoted 2 lines
Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
for EP93xx:
Quoted 72 lines
---
arch/arm/Kconfig | 15 ++++++--------- arch/arm/configs/am200epdkit_defconfig | 1 - arch/arm/configs/aspeed_g4_defconfig | 1 -arch/arm/configs/assabet_defconfig | 1 + arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/axm55xx_defconfig | 1 - arch/arm/configs/bcm2835_defconfig | 1 -arch/arm/configs/clps711x_defconfig | 1 -
arch/arm/configs/collie_defconfig | 1 -
arch/arm/configs/davinci_all_defconfig | 1 -
arch/arm/configs/dove_defconfig | 1 -
arch/arm/configs/ep93xx_defconfig | 1 -
arch/arm/configs/footbridge_defconfig | 1 +
arch/arm/configs/gemini_defconfig | 1 -
arch/arm/configs/h3600_defconfig | 1 -
arch/arm/configs/hisi_defconfig | 1 -
arch/arm/configs/imx_v4_v5_defconfig | 1 -
arch/arm/configs/integrator_defconfig | 1 -
arch/arm/configs/ixp4xx_defconfig | 1 -
arch/arm/configs/jornada720_defconfig | 1 -
arch/arm/configs/keystone_defconfig | 1 -
arch/arm/configs/lpc32xx_defconfig | 1 -
arch/arm/configs/mmp2_defconfig | 1 -
arch/arm/configs/moxart_defconfig | 1 -
arch/arm/configs/multi_v4t_defconfig | 1 -
arch/arm/configs/multi_v5_defconfig | 1 -
arch/arm/configs/mv78xx0_defconfig | 2 --
arch/arm/configs/mvebu_v5_defconfig | 1 -
arch/arm/configs/mxs_defconfig | 1 -
arch/arm/configs/neponset_defconfig | 1 +
arch/arm/configs/netwinder_defconfig | 1 +
arch/arm/configs/nhk8815_defconfig | 1 -
arch/arm/configs/omap1_defconfig | 2 --
arch/arm/configs/orion5x_defconfig | 2 --arch/arm/configs/pxa168_defconfig | 2 -- arch/arm/configs/pxa3xx_defconfig | 2 -- arch/arm/configs/pxa910_defconfig | 2 --arch/arm/configs/pxa_defconfig | 1 -
arch/arm/configs/rpc_defconfig | 1 +
arch/arm/configs/spear13xx_defconfig | 1 -
arch/arm/configs/spitz_defconfig | 1 -
arch/arm/configs/versatile_defconfig | 1 -
arch/arm/configs/vt8500_v6_v7_defconfig | 1 -
arch/arm/configs/wpcm450_defconfig | 1 -44 files changed, 11 insertions(+), 53 deletions(-)arch/arm/Kconfig +0
-0@@ -1153,17 +1153,14 @@ config ARM_PATCH_IDIVconfig AEABI
bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \
!CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANGarch/arm/Kconfig +1
-1- default CPU_V7 || CPU_V7M || CPU_V6 || CPU_V6K || CC_IS_CLANG + default yhelp
arch/arm/Kconfig +3
-3- This option allows for the kernel to be compiled using the latest - ARM ABI (aka EABI). This is only useful if you are using a user - space environment that is also compiled with EABI. + The Arm EABI is the default ABI on all modern Linux + distributions, replacing the obsolete and "OABI" that was + commonly used on ARMv4 distributions before ca. 2013.arch/arm/Kconfig +2
-5- Since there are major incompatibilities between the legacy ABI and - EABI, especially with regard to structure member alignment, this - option also changes the kernel syscall calling convention to - disambiguate both ABIs and allow for backward compatibility support - (selected with CONFIG_OABI_COMPAT). + Everyone should enable this, as support for OABI user space + was dropped in gcc-4.8 and most distributions after ca. 2013.
Quoted 4 lines
configOABI_COMPAT
bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
[]
Quoted 12 lines
arch/arm/configs/ep93xx_defconfig +0
-0@@ -18,7 +18,6 @@ CONFIG_MACH_EDB9315=yCONFIG_MACH_EDB9315A=y
CONFIG_MACH_TS72XX=y
CONFIG_MACH_VISION_EP9307=y
-CONFIG_AEABI=yCONFIG_CMDLINE="console=ttyAM0,115200root=/dev/nfs ip=bootp"CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
Signature · 3 lines
Alexander Sverdlin Siemens AG www.siemens.com
Linus Walleij
maintainerRe: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
In reply to Arnd BergmannHi Arnd,
thanks for your patch!
arch/arm/mm/Kconfig config CPU_LITTLE_ENDIAN · line 781
Quoted 3 lines · Arnd Bergmann
config
CPU_BIG_ENDIANarch/arm/mm/Kconfig +1
-1- bool "Build big-endian kernel" + bool "Build big-endian kernel (DEPRECATED)"
I'm not so sure about this patch because it will look like IXP4XX is using a deprecated feature. The IXP4xx actually has many OpenWrt users.
As mentioned on IRC I tried *very* hard to boot IXP4xx in LE mode, by adding some code to the kernel to force-switch to LE but failed:
the bit in cp15 can be cleared for sure but after this the machine nevertheless stays in BE mode.
If someone has done this successfully and can tell of magic tricks I'm all ears...
Quoted 1 line
+ depends on
ARCH_MULTI_V5|| BROKEN
... but this is all fine.
Yours,
Linus Walleij
Re: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
Quoted 6 lines · Linus Walleij
Hi Arnd,
thanks for your patch!
On Wed, Jul 1, 2026 at 11:25 PM Arnd Bergmann <[email protected]> wrote:
Quoted 7 lines
Review
Quoted 3 lines
config
CPU_BIG_ENDIAN(quoted diff) +1
-1- bool "Build big-endian kernel" + bool "Build big-endian kernel (DEPRECATED)"I'm not so sure about this patch because it will look like IXP4XX is using a deprecated feature. The IXP4xx actually has many OpenWrt users.
How about the version below? If you like that better, I'll give it a thorough build test and use that for v3.
Arnd
arch/arm/mach-ixp4xx/Kconfig +0 -1
@@ -2,7 +2,6 @@ menuconfig ARCH_IXP4XX bool "IXP4xx-based platforms" depends on ARCH_MULTI_V5 - depends on CPU_BIG_ENDIAN select ARM_APPENDED_DTB # Old Redboot bootloaders deployed select CPU_XSCALE select GPIO_IXP4XX
arch/arm/mm/Kconfig +14 -20
@@ -796,38 +796,32 @@ choice config CPU_LITTLE_ENDIAN bool "Built little-endian kernel" + depends on !ARCH_IXP4XX help Say Y if you plan on running a kernel in little-endian mode. This is the default and is used in practically all modern user space builds. -config CPU_BIG_ENDIAN - bool "Build big-endian kernel (DEPRECATED)" - depends on ARCH_MULTI_V5 || BROKEN - depends on !LD_IS_LLD - help - Say Y if you plan on running a kernel in big-endian mode. - This works on many machines using ARMv6 or newer processors - but requires big-endian user space. - - The only ARMv5 platform with big-endian support is - Intel IXP4xx. - -endchoice - config CPU_ENDIAN_BE8 - bool - depends on CPU_BIG_ENDIAN - default CPU_V6 || CPU_V6K || CPU_V7 || CPU_V7M + bool "Build big-endian kernel (DEPRECATED)" + depends on BROKEN + depends on ARCH_MULTI_V6 || ARCH_MULTI_V7 + select CPU_BIG_ENDIAN help Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors. + This is deprecated and will likely be removed in the future. + config CPU_ENDIAN_BE32 - bool - depends on CPU_BIG_ENDIAN - default !CPU_ENDIAN_BE8 + bool "Build big-endian kernel" + depends on ARCH_IXP4XX + select CPU_BIG_ENDIAN help Support for the BE-32 (big-endian) mode on pre-ARMv6 processors. +endchoice + +config CPU_BIG_ENDIAN + bool config CPU_HIGH_VECTOR depends on !MMU && CPU_CP15 && !CPU_ARM740T
Re: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
Hi Arnd,
arch/arm/mm/Kconfig choice · line 813
Quoted 12 lines · Arnd Bergmann
config
CPU_ENDIAN_BE8arch/arm/mm/Kconfig +5
-3- bool - depends on CPU_BIG_ENDIAN - default CPU_V6 || CPU_V6K || CPU_V7 || CPU_V7M + bool "Build big-endian kernel (DEPRECATED)" + depends on BROKEN + depends on ARCH_MULTI_V6 || ARCH_MULTI_V7 + select CPU_BIG_ENDIAN help Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors. + This is deprecated and will likely be removed in the future.
Maybe it makes sense to add a 'transitional' to this option?
- Julian Braha
Re: [PATCH v2 06/19] ARM: mark CPU_ENDIAN_BE8 as deprecated
In reply to Arnd BergmannQuoted 10 lines · Arnd Bergmann
Quoted 7 lines
Review
Quoted 3 lines
config
CPU_BIG_ENDIAN(quoted diff) +1
-1- bool "Build big-endian kernel" + bool "Build big-endian kernel (DEPRECATED)"I'm not so sure about this patch because it will look like IXP4XX is using a deprecated feature. The IXP4xx actually has many OpenWrt users.
How about the version below? If you like that better, I'll give it a thorough build test and use that for v3.
We figured out LE on IXP4xx so I'm fine with this now, provided we can fold in the LE32 fixes for IXP4xx at the same time.
Yours,
Linus Walleij
Re: [PATCH v2 05/19] ARM: turn CONFIG_ATAGS off by default
In reply to Arnd BergmannHi Arnd,
Quoted 16 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
Only a very small number of machines remain that rely on traditional board files with the ATAGS boot data instead of devicetree, and we have not accepted new ones for a decade.
Most of the remaining ones are on their way out of the kernel, but the
Kconfigoption that controls ATAGS is still enabled by default.To reflect the actual status of ATAGS support and alert the remaining users of upstream and out-of-tree platforms with this, chanyge it to being default-disabled and add a dependency on
CONFIG_EXPERT.
Quoted 7 lines
The board specific defconfig files that rely on ATAGS are changed to turn on both EXPERT and ATAGS if they were not doing thath already, and the ones that explicitly turned it off before no longer need to.
Acked-by Linus Walleij <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>
Thanks for your patch, which is now commit 4d9226b820c165b7 ("ARM:
turn CONFIG_ATAGS off by default") in soc/for-next.
Quoted 13 lines
arch/arm/Kconfig +1
-5@@ -1390,12 +1390,15 @@ config ARCH_WANT_FLAT_DTB_INSTALL config ATAGS bool "Support for the traditional ATAGS boot data passing" - default y + depends on EXPERT help - This is the traditional way of passing data to the kernel at boot - time. If you are solely relying on the flattened device tree (or - the ARM_ATAG_DTB_COMPAT option) then you may unselect this option - to remove ATAGS support from your kernel binary.
arch/arm/Kconfig config ARCH_WANT_FLAT_DTB_INSTALL · line 1404
Quoted 10 lines
arch/arm/Kconfig +7
-0+ This is the traditional way of passing data to the kernel at + boot but is now only used by a few of the oldest ARMv4 and + ARMv5 machines. Users that still rely on ATAGS should plan + on migrating to devicetree based booting. + + Support for ATAGS will be removed when the last machine using + it is either converted to DT or removed. config DEPRECATED_PARAM_STRUCT bool "Provide old way to pass kernel parameters"
I don't know how much of this is used by systems with old boot loaders that use a combination of (appended) DT and ATAGS.
E.g. the old U-Boots on Marzen (R-Car H1) and KZM-A9-GT (SH-Mobile AG5) rely on CONFIG_ARM_ATAG_DTB_COMPAT=y to pass the kernel command line, and that still seems to work fine without ATAGS.
Note that to boot a proper multi-platform kernel on KZM-A9-GT, I still need "[PATCH v2 1/2] ARM: decompressor: support memory start validation for appended DTB"[1], which RMK doesn't like. That patch is so old that I forgot how to make upstream boot on KZM-A9-GT without it...
Anyway, it looks like all my boards boot without CONFIG_ATAGS. Thanks!
[1] https://lore.kernel.org/[email protected]/
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds