1614 2011-10-04 13:29:00 +0000 Target module build 2012-07-24 12:08:46 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel unspecified x86 Multiple VERIFIED FIXED (P1)(patch review) (Jun 28) Medium enhancement 1.3 M2 1 song.liu dvhart bruce.ashfield dvhart jessica.zhang kishore.k.bodke laurentiu.serban poky.bs.watcher poky.watcher richard.purdie tom.zanussi --- --- --- oldest_to_newest 16682 0 song.liu 2011-10-04 13:29:00 +0000 Allow for building kernel modules on the target device (on janitor's list?) 16746 1 dvhart 2011-10-06 10:20:05 +0000 This would involve reworking the kernel recipes to install the required kernel headers, Makefiles, etc. on the target. I wouldn't rank this as particularly high priority personally unless have seen more demand for it than I have. 16875 2 tom.zanussi 2011-10-14 11:38:48 +0000 ECG asked me about this yesterday, and it's not the first time. I think this should be given some amount of priority. 18049 3 dvhart 2012-01-10 08:20:22 +0000 Moving to Medium and M3. We may need another owner for this, I'll ask for volunteers if needed. 20661 4 kishore.k.bodke 2012-04-18 17:11:08 +0000 Updating with my comments. This is nice to have, as we are getting this request from the BSP requestors. They want to build and test the out of tree kernel modules on the target. 20665 5 dvhart 2012-04-18 17:54:25 +0000 Kishore, can you provide a reason for why they want to do this? It is more inline with the Yocto Project development methodologies to add the modules you want to a simple recipe, following the hello-mod recipe in meta-skeleton, and build them as part of the image. Typically the target is not meant to be the development platform. It can be - but I'd like to understand WHY people are wanting to development this way? Is it just not wanting how to work within the Yocto Project environment? 20693 6 kishore.k.bodke 2012-04-19 01:56:09 +0000 The details what I have from the BSP requestors, is that instead of going through a recipe, they directly want to use the target machine as a development machine to modify and recompile and load. They want to shift from the existing Fedora based development to Yocto based development system. For every new version of driver alpha/beta/gold , doing from a recipe and building the image is a time consuming. Instead they have one image booted and can build different versions of driver on the target machine directly. 20695 7 dvhart 2012-04-19 02:57:47 +0000 We can certainly work with them to make that process much less time consuming with the use of prebuilt images, etc. However, a transition goes more smoothly if small changes are made instead of everything all at once. I can see the desire for this feature. 20994 8 dvhart 2012-05-02 16:29:15 +0000 Switching to P1 due to popular demand. 22566 9 dvhart 2012-06-25 23:34:03 +0000 I have this working with the exception of having to first build the kernel scripts binaries on the target before building a module. I've solicited ideas on how to build the target-arch scripts binaries and package them along with the kernel-headers package. 22960 10 richard.purdie 2012-07-10 15:33:20 +0000 Fixed im master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=68a8caa738caa25f313a0bccfd8179cc5584afa5 23435 11 laurentiu.serban 2012-07-24 12:08:46 +0000 Verified in 0ffb02eec2beaea27ff0ec9d3d31b0a09e675a4c A kernel module was built and loaded on the target.