On Thu, Mar 12, 2026 at 9:22 PM Alexander Kanavin <[email protected]> wrote: > > On Thu, 5 Mar 2026 at 06:35, Alistair Francis via > lists.openembedded.org <[email protected]> > wrote: > > When bulding Linux with kernel modules by default they aren't included > > in the qemux86-64 machine. Let's ensure that they are included by > > setting the MACHINE_EXTRA_RRECOMMENDS to include " ernel-modules". > > > > This is already done for the qemuppc64, qemuloongarch and qemuriscv > > machines. > > -MACHINE_EXTRA_RRECOMMENDS = "kernel-module-snd-ens1370 > > kernel-module-snd-rawmidi" > > +MACHINE_EXTRA_RRECOMMENDS += " kernel-modules" > > +MACHINE_EXTRA_RRECOMMENDS += " kernel-module-snd-ens1370 > > kernel-module-snd-rawmidi" > > The consensus in the patch review meeting was that BSPs forcing *all* > of the kernel modules into images is actually an anti-pattern that > should be avoided. It should only list specific, known to be useful
This is very confusing to users though. If I use menuconfig to enable a kernel module ```shell MACHINE=qemux86-64 bitbake virtual/kernel -c do_menuconfig ``` then I expect that module to be installed, but currently it's not. So even with a module enabled it's not being installed, which is very confusing and difficult for people to debug. Alistair > items, similar to how linux-firmware or python modules are packaged > and installed. This has unfortunately gotten into qemuriscv > definitions, but the correct approach would be to replace that with > specific module lists, e.g. by replicating autobuilder tests for that > target: > > https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json > > Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#233015): https://lists.openembedded.org/g/openembedded-core/message/233015 Mute This Topic: https://lists.openembedded.org/mt/118147967/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
