On Tue, Jul 7, 2015 at 5:55 AM, Philip Balister <[email protected]> wrote: > On 07/06/2015 09:16 PM, Richard Cagley wrote: >> I have a kernel module that shows up in my build work directory after >> I configure the kernel accordingly >> build/tmp-glibc/work/zedboard_zynq7-oe-linux-gnueabi/linux-xlnx/3.14-xilinx+gitAUTOINC+2b48a8aeea-r0/image/lib/modules/3.14.2-xilinx/kernel/drivers/dma/xilinx/vdmatest.ko >> >> But, when I add "kernel-modules" to my IMAGE_INSTALL in local.conf I >> don't see vdmatest.ko show up in the resultant root filesystem after I >> run bitbake core-image-minimal-dev and untar the image >> >> Is there a way to tell yocto to install all kernel modules or a step >> I've missed? >> > > I have: > > MACHINE_EXTRA_RRECOMMENDS = "kernel-modules" > > in my machine conf, > Wow, thanks. I spent a lot of time trying to figure out that one. I stuck it in local.conf for now but I guess the machine.conf would eventually make more sense.
> Make sure you have buildhistory in your user classes. That creates files > that are very helpful for working out what is actually in the generated > packages. > thanks for the tip. I just turned this on and will try to leverage it in the future. -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
