From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: openembedded-core@lists.openembedded.org
Cc: poky@lists.yoctoproject.org, Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: [PATCH 2/3] kernel-yocto.bbclass: support modular kernel configs
Date: Wed, 23 Apr 2025 11:02:45 +0300 [thread overview]
Message-ID: <20250423080246.128723-2-mikko.rapeli@linaro.org> (raw)
In-Reply-To: <20250423080246.128723-1-mikko.rapeli@linaro.org>
Compile many kernel drivers as modules when recipe sets
MODULAR_KERNEL = "true"
This likely requires support for initramfs which includes
kernel modules needed to mount the rootfs.
SCC_OPTS can be used to add arguments to scc kernel config
generation call.
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
meta/classes-recipe/kernel-yocto.bbclass | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/kernel-yocto.bbclass b/meta/classes-recipe/kernel-yocto.bbclass
index cef6b9ec3f..f98720bcec 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -26,6 +26,12 @@ KCONF_BSP_AUDIT_LEVEL ?= "0"
KMETA_AUDIT ?= "yes"
KMETA_AUDIT_WERROR ?= ""
+# most drivers as built in (default), or as modules
+MODULAR_KERNEL = "false"
+
+# options to scc
+SCC_OPTS ?= "${@bb.utils.contains('MODULAR_KERNEL', 'true', '-DMODULE_OR_Y=m', '', d)}"
+
# returns local (absolute) path names for all valid patches in the
# src_uri
def find_patches(d,subdir):
@@ -298,7 +304,7 @@ do_kernel_metadata() {
elements="`echo -n ${bsp_definition} $sccs_defconfig ${sccs} ${patches} $KERNEL_FEATURES_FINAL`"
if [ -n "${elements}" ]; then
echo "${bsp_definition}" > ${S}/${meta_dir}/bsp_definition
- scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} $sccs_defconfig $bsp_definition $sccs $patches $KERNEL_FEATURES_FINAL
+ scc ${SCC_OPTS} --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} $sccs_defconfig $bsp_definition $sccs $patches $KERNEL_FEATURES_FINAL
if [ $? -ne 0 ]; then
bbfatal_log "Could not generate configuration queue for ${KMACHINE}."
fi
--
2.43.0
next prev parent reply other threads:[~2025-04-23 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 8:02 [PATCH 1/3] kern-tools-native: update to support modular kernel builds Mikko Rapeli
2025-04-23 8:02 ` Mikko Rapeli [this message]
2025-04-23 12:30 ` [poky] [PATCH 2/3] kernel-yocto.bbclass: support modular kernel configs Bruce Ashfield
2025-04-23 12:40 ` Mikko Rapeli
2025-04-23 8:02 ` [PATCH 3/3] linux-yocto: build modular kernel on genericarm64 Mikko Rapeli
2025-04-23 12:31 ` [OE-core] " Bruce Ashfield
2025-04-23 12:31 ` [poky] [PATCH 1/3] kern-tools-native: update to support modular kernel builds Bruce Ashfield
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=20250423080246.128723-2-mikko.rapeli@linaro.org \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@lists.yoctoproject.org \
/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