From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: chalianis1@gmail.com, s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/7] arm: efi: add a generic efi machine.
Date: Thu, 4 Sep 2025 10:20:27 +0200 [thread overview]
Message-ID: <c7d7bfa9-c165-4ad0-a4a2-76c0de24c56c@pengutronix.de> (raw)
In-Reply-To: <20250831035542.1623695-4-chalianis1@gmail.com>
Hi,
On 31.08.25 05:55, chalianis1@gmail.com wrote:
> From: Chali Anis <chalianis1@gmail.com>
>
> add a generic arm64 machine that can select the CPU_V8 and the
> required efi payload minimal configs. this machine permits to have
> a clean arm64 efi payload, idealy we don't need the other machine
> that comes from multi arch since they execute code that is specific
> for the correspondig hardware. with this generic efi machine the
> barebox log shell is more clean. to get a pure clean efi payload
> you need to unselect all the other arch machines and keep only the
> EFI ARM64.
>
> Signed-off-by: Chali Anis <chalianis1@gmail.com>
> ---
> arch/arm/Kconfig | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index cce71b50eb04..0a098440ddde 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -254,6 +254,18 @@ config ARCH_ZYNQMP
> select GPIOLIB
> select HAS_MACB
>
> +config EFI_ARM64
Thinking about it, this doesn't really fit into the existing model.
We have CONFIG_EFI_PAYLOAD, which when enabled gives _all_ images
an EFI stub.
I think it's better to just give CPU_V7 and CPU_V8 prompts.
Then they can be enabled for the barebones EFI-only use case alongside
CONFIG_EFI_PAYLOAD. CONFIG_EFI_PAYLOAD should have its depends on
COMPILE_TEST removed as last patch in your series then I think (or
before last if you add a dedicated efi_defconfig).
> + bool "EFI on ARM64"
Generally, we should call it EFI payload to differentiate from
EFI loader (firmware)
> + select CPU_V8
> + select CPU_SUPPORTS_64BIT_KERNEL
Symbol doesn't exist on ARM.
> + select HAVE_EFI_PAYLOAD
Already selected by CPU_64
> + select EFI_PAYLOAD
> + select BOOTM_FITIMAGE
select means it can't be deselected, which is not needed here.
> + select CLOCKSOURCE_EFI
> + select DRIVER_VIDEO_EFI_GOP
It's reasonable to disable GOP if the device is headless anyway.
You can give the DRIVER_VIDEO_EFI_GOP a default y though if you like,
because many (most?) users will likely want to use GOP.
Point is moot with above suggested change though.
> + depends on 64BIT
> + default y if ARCH_MULTIARCH
> +
> source "arch/arm/cpu/Kconfig"
> source "arch/arm/mach-at91/Kconfig"
> source "arch/arm/mach-bcm283x/Kconfig"
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-09-04 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 3:55 [PATCH 1/7] drivers: video: efi-gop: fix null reference pointer chalianis1
2025-08-31 3:55 ` [PATCH 2/7] efi: video: gop: remove dependency to x86 chalianis1
2025-09-02 9:20 ` Ahmad Fatoum
2025-08-31 3:55 ` [PATCH 3/7] efi: payload: initrd: implement efi initrd media protocol chalianis1
2025-08-31 3:55 ` [PATCH 4/7] arm: efi: add a generic efi machine chalianis1
2025-09-03 7:14 ` Sascha Hauer
2025-09-04 8:20 ` Ahmad Fatoum [this message]
2025-09-05 0:16 ` anis chali
2025-08-31 3:55 ` [PATCH 5/7] lib: fdt: add lib fdt padding size chalianis1
2025-08-31 3:55 ` [PATCH 6/7] efi: payload: add support for efi stub boot and fit image chalianis1
2025-09-03 7:11 ` Sascha Hauer
[not found] ` <CAL+1fyD6Jevxx_wP00caRoXe0yRmM6uScJN8W3fkRVNVfLRj1Q@mail.gmail.com>
[not found] ` <aLksEfZ3-YiEL-xN@pengutronix.de>
[not found] ` <CAL+1fyA5FtjLfRDbF-dpxr=T6kL=hrF8pr6wJk5aR1X=5CEFUg@mail.gmail.com>
2025-09-04 6:48 ` Sascha Hauer
2025-09-04 6:55 ` Ahmad Fatoum
2025-09-04 9:03 ` Ahmad Fatoum
2025-09-04 22:44 ` anis chali
2025-08-31 3:55 ` [PATCH 7/7] efi: payload: add options for FDT force and initrd direct install chalianis1
2025-09-04 9:19 ` Ahmad Fatoum
2025-09-04 22:30 ` anis chali
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=c7d7bfa9-c165-4ad0-a4a2-76c0de24c56c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.com \
--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