From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <dixitparmar19@gmail.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v2] ref-manual: document KERNEL_SPLIT_MODULES variable
Date: Wed, 18 Jun 2025 14:59:57 +0200 [thread overview]
Message-ID: <DAPOERTPGVZQ.1S2ZZBVVMS1N6@bootlin.com> (raw)
In-Reply-To: <9960.1750248888618731264@lists.yoctoproject.org>
On Wed Jun 18, 2025 at 2:14 PM CEST, Dixit Parmar via lists.yoctoproject.org wrote:
> Will fix the ref->term typo and the take your suggestion on rewording.
>
> There seem to be confusion related to the kernel package name, however I feel
> it was additional information. I shall remove the mention of the kernel
> package name (keep the variable reference only) for simplicity in next
> version.
Looking forward to it!
> Yes, you would be able to install "all" the kernel-modules without bothering
> about KERNEL_SPLIT_MODULES. The issue is having autoload .conf file being
> installed or not when KERNEL_MODULE_AUTOLOAD is having your modules listed to
> be autoloader. When KERNEL_SPLIT_MODULES = 0 the .conf files for driver
> autoload and probeconf is not getting generated.
This sounds like a bug to me, no? Why would someone expect setting
KERNEL_SPLIT_MODULES to 0 have the autoload files missing?
I ran a some tests. So when I set KERNEL_SPLIT_MODULES to 1, and
KERNEL_MODULE_AUTOLOAD to "xt_limit", a kernel-module-xt-limit.ipk package is
generated like so:
├── etc
│ └── modules-load.d
│ └── xt_limit.conf
└── lib
└── modules
└── 6.12.30-yocto-standard
└── kernel
└── net
└── netfilter
└── xt_limit.ko
When KERNEL_SPLIT_MODULES is set to 0, only one kernel-modules.ipk package is
generated, and does _not_ contain xt_limit.conf, but only xt_limit.ko. To me
this sounds like a bug, what do you think?
I would _not_ describe that behavior in the documentation for the
KERNEL_SPLIT_MODULES variables.
The fact that "kernel-modules" is still available when KERNEL_SPLIT_MODULES = 1
is simply because a "fake" kernel-modules.ipk package is generated, and depends
on the other kernel-module-* packages - so you can ignore my remark in my
previous message.
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-18 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 10:44 [PATCH v2] ref-manual: document KERNEL_SPLIT_MODULES variable Dixit Parmar
2025-06-10 8:55 ` [docs] " Antonin Godard
2025-06-10 9:20 ` Antonin Godard
2025-06-18 12:14 ` Dixit Parmar
2025-06-18 12:59 ` Antonin Godard [this message]
2025-06-18 13:19 ` Dixit Parmar
2025-06-18 13:42 ` [docs] " Antonin Godard
2025-06-21 6:48 ` Dixit Parmar
2025-07-01 8:37 ` Antonin Godard
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=DAPOERTPGVZQ.1S2ZZBVVMS1N6@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=dixitparmar19@gmail.com \
--cc=docs@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