Hi Hans, Le Fri, 8 Mar 2013 13:08:21 +0100, Hans Beckérus <[email protected]> a écrit :
> Hi. I have built some custom kernel modules (.ko) using a .bb that > inherits from the module.bbclass. There is one main kernel module and > the rest are dependent on the first. Building and installing the > modules to the rootfs works fine. Next question is how do I control > what actual modules are loaded at boot, or actually how do I control > this through Yocto? To my surprise one of the kernel module loaded > automatically!? How could this happen? I did not have an entry for it > in /etc/modules. And what do I need to do to actually add entries to > /etc/modules? Or is there some other mechanism that I should use. I > tried going through the module.bbclass but must admit I lost it > somewhere in the middle ;) Any guidance would be appreciated. > when the module is built by the kernel recipe you can use : module_autoload and you can see somme usage examples here : http://cgit.openembedded.org/meta-handheld/tree/conf/machine/palmtx.conf http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/palm.inc maybe you could get inspiration from kernel.bbclass to do the same thing in your recipe. Eric _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
