From: chalianis1@gmail.com
To: s.hauer@pengutronix.de, a.fatoum@barebox.org
Cc: barebox@lists.infradead.org,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Chali Anis <chalianis1@gmail.com>
Subject: [PATCH v3 01/11] ARM: cpu: allow selecting CPU_V7/CPU_V8 directly
Date: Tue, 16 Sep 2025 00:01:45 -0400 [thread overview]
Message-ID: <20250916040155.814159-1-chalianis1@gmail.com> (raw)
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
We currently lack a way to build a barebox EFI payload on ARM without
enabling some other subarchitecture. As CONFIG_EFI_PAYLOAD has a global
effect and adds EFI stubs to all enabled board, an EFI subarchitecture
doesn't fit into our current model.
Instead, let's make it possible to enable either CONFIG_CPU_V8 or
CONFIG_CPU_V7 directly.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Link: https://lore.barebox.org/20250904081626.93182-1-a.fatoum@pengutronix.de
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Chali Anis <chalianis1@gmail.com>
---
arch/arm/cpu/Kconfig | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/arm/cpu/Kconfig b/arch/arm/cpu/Kconfig
index e61bcadc8c35..fe0d1e470578 100644
--- a/arch/arm/cpu/Kconfig
+++ b/arch/arm/cpu/Kconfig
@@ -79,12 +79,15 @@ config CPU_V6
# ARMv7
config CPU_V7
- bool
+ bool "Generic ARMv7 support"
+ depends on 32BIT
select CPU_32v7
# ARMv8
config CPU_V8
- bool
+ bool "Generic ARMv8 support"
+ default y
+ depends on 64BIT
select CPU_64v8
select ARM_EXCEPTIONS
select GENERIC_FIND_NEXT_BIT
--
2.34.1
next reply other threads:[~2025-09-16 4:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 4:01 chalianis1 [this message]
2025-09-16 4:01 ` [PATCH v3 02/11] efi: payload: split image handling from legacy handover boot support chalianis1
2025-09-16 4:01 ` [PATCH v3 03/11] efi: payload: add support for efi stub boot chalianis1
2025-09-16 4:01 ` [PATCH v3 04/11] efi: payload: add support for fit image chalianis1
2025-09-16 4:01 ` [PATCH v3 05/11] efi: payload: make selectable without COMPILE_TEST chalianis1
2025-09-16 4:01 ` [PATCH v3 06/11] arm: efi: add a generic defconfig for v8 efi payload, chalianis1
2025-09-16 4:01 ` [PATCH v3 07/11] efi: payload: initrd: implement efi initrd media protocol chalianis1
2025-09-16 4:01 ` [PATCH v3 08/11] common: filetype: add x86 linux filetype chalianis1
2025-09-16 4:01 ` [PATCH v3 09/11] efi: payload: early-mem: helps to correctly boot x86 linux chalianis1
2025-09-16 4:01 ` [PATCH v3 10/11] efi: payload: bootm: add x86 efi stub boot support chalianis1
2025-09-16 4:01 ` [PATCH v3 11/11] lib: fdt: remove FDT_PADDING chalianis1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250916040155.814159-1-chalianis1@gmail.com \
--to=chalianis1@gmail.com \
--cc=a.fatoum@barebox.org \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox