Hi, >Wasn't aware that you need to include that in an image. >Thought this was simply bitbake magic.
the package kernel-modules-xxxx.ipk is a meta package containing runtime dependencies to all modules compiled with the kernel, created while bitbaking a kernel (kernel.bbclass). It should trigger an install of all configured modules to the image. >Is there ever a case when you do not want to have the modules >that you so cunningly configured for your kernel build??? It may be someone wants to have a "general" modulized kernel, but depending on the machine/distro capabilities/needs only some of the modules should be available, then you are able to install the needed kernel-module-xxx.ipk packages only. This mainly saves space and limits the available functionality to the needs. If the system is running well, it may be better to compile all modules into the kernel. If the image includes task-boot, the modules to be installed are configured in <machine>.conf. Regards Wolfgang _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
