[PATCH 3/4] ARM: allow CONFIG_ARM_MMU_PERMISSIONS together with EFI_RUNTIME

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

From: Ahmad Fatoum <a.fatoum@barebox.org>

The exclusion was added because the MMU permission code could only
handle a single text/rodata section, while EFI_RUNTIME adds a second
set, and because EFI payloads expect RWX mappings.

Both reasons are gone: barebox proper is a proper ELF now and PBL
applies permissions from the PT_LOAD segment flags, which since the
preceding commits include separate segments for the EFI runtime
services code and data, and code-type EFI page allocations are
remapped executable at allocation time.

As ARM_MMU_PERMISSIONS defaults to y, the multi_v8_efiloader and
multi_v8_efi CI configurations start testing W^X together with the
EFI loader with this commit.

Assisted-by: Claude:fable-5
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
 arch/arm/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 02580611d9c3..47089df2a0e1 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -468,7 +468,7 @@ config ARM_UNWIND
 
 config ARM_MMU_PERMISSIONS
 	bool "Map with extended RO/X permissions"
-	depends on MMU && !EFI_RUNTIME
+	depends on MMU
 	default y
 	help
 	  Enable this option to map readonly sections as readonly, executable
-- 
2.47.3