From: Elvis D. <elv...@ma...> - 2009-05-19 17:12:33
|
Hi, I think what you should do is, run the following command, after you have built a omap3-console-image, bitbake -c menuconfig linux-omap3-2.6.29 Then configure each driver to load as a module, instead of statically linking to the kernel image. i.e. see if the corresponding driver has an <M> option next to it. If it is a <*> then it means that it is statically linked in. After that, save your changes, and copy the .config file from the overo-oe/tmp/..../linux-omap3-2.6.29/git folder, and save it as defconfig in your overo-oe/recipes/linux/linux-omap3-2.6.29/overo folder. and rebuild the kernel image bitbake -c clean linux-omap3-2.6.29 bitbake -c rebuild linux-omap3-2.6.29 bitbake -c rebuild omap3-console-image Best regards, Elvis Dowson On May 19, 2009, at 8:57 PM, jsarao wrote: > > bump > > -- > View this message in context: http://www.nabble.com/Compiling-kernel-modules-for-Overo-tp22934466p23610559.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |