Hi, I'm looking now already for a couple of weeks for a solution for this problem.
In our system we have a recipe which loads from an GIT server our driver packet which contains some HW specific drivers which shall be used as kernel modules. For this purpose we have our own do_configure(), do_compile(), do_install(). Building to *.ko files still works fine, and I can see them in the image/ and package/ folder kirkstone: - image/lib/modules/5.15.150-rt72-yocto-preempt-rt/misc/men_bb_chameleon_pcitbl.ko - package/lib/modules/5.15.150-rt72-yocto-preempt-rt/misc/men_bb_chameleon_pcitbl.ko scarthgap: - image/lib/modules/6.6.35-rt31-yocto-preempt-rt/misc/men_bb_chameleon_pcitbl.ko - package/lib/modules/6.6.35-rt31-yocto-preempt-rt/misc/men_bb_chameleon_pcitbl.ko But in kirkstone also something is created in packes-split/ and deploy-rpms/ folders (and also in some others like pkgdata* and target/OBJ ): - packages-split/kernel-module-men-bb-chameleon-pcitbl-5.15.150-rt72-yocto-preempt-rt/lib/modules/5.15.150-rt72-yocto-preempt-rt/misc/men_bb_chameleon_pci - deploy-rpms/f75p/kernel-module-men-bb-chameleon-pcitbl-5.15.150-rt72-yocto-preempt-rt-1.0-r0.f75p.rpm This is not the case for the scarthgap build. So I guess something is missing in my recipe to get the build in scarthgap successful and to get a *.rpm file for every of my driver kernel-modules. Happy for every hint :-) Thx, Markus
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63696): https://lists.yoctoproject.org/g/yocto/message/63696 Mute This Topic: https://lists.yoctoproject.org/mt/107890718/21656 Mute #kernelmodule:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernelmodule Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #scarthgap:https://lists.yoctoproject.org/g/yocto/mutehashtag/scarthgap Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
