From: chalianis1@gmail.com
To: s.hauer@pengutronix.de, a.fatoum@pengutronix.de
Cc: barebox@lists.infradead.org, Chali Anis <chalianis1@gmail.com>
Subject: [PATCH 7/7] efi: payload: add options for FDT force and initrd direct install
Date: Sat, 30 Aug 2025 23:55:42 -0400 [thread overview]
Message-ID: <20250831035542.1623695-7-chalianis1@gmail.com> (raw)
In-Reply-To: <20250831035542.1623695-1-chalianis1@gmail.com>
From: Chali Anis <chalianis1@gmail.com>
Signed-off-by: Chali Anis <chalianis1@gmail.com>
---
efi/Kconfig | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/efi/Kconfig b/efi/Kconfig
index 84f670fd23d3..c3811574920d 100644
--- a/efi/Kconfig
+++ b/efi/Kconfig
@@ -50,4 +50,21 @@ config EFI_PAYLOAD_DEFAULT_PATH
endif
+config EFI_FDT_FORCE
+ bool "Force EFI provided FDT"
+ default n
+ help
+ with this options we keep the fdt passed by EFI in the
+ system configuration table, EFI has to suppot FDT otherwise
+ an empty fdt will be generated when linux boots by efi.
+
+config EFI_INITRD_INSTALL
+ bool "Install the initramfs by barebox"
+ default n
+ help
+ with this option barebox will install the initrd to the
+ system configuration table, same as what kernel do after
+ calling read file2 boot services, in this case the initrd
+ will be read directly by the kernel as an initramfs.
+
endmenu
--
2.34.1
prev parent reply other threads:[~2025-08-31 3:56 UTC|newest]
Thread overview: 7+ 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-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-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-08-31 3:55 ` chalianis1 [this message]
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=20250831035542.1623695-7-chalianis1@gmail.com \
--to=chalianis1@gmail.com \
--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