| Summary: | Target module build | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Song Liu <song.liu> |
| Component: | kernel | Assignee: | Darren Hart <dvhart> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bruce.ashfield, dvhart, jessica.zhang, kishore.k.bodke, laurentiu.serban, poky.bs.watcher, poky.watcher, richard.purdie, tom.zanussi |
| Version: | unspecified | ||
| Target Milestone: | 1.3 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P1)(patch review) (Jun 28) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Song Liu
2011-10-04 13:29:00 UTC
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. ECG asked me about this yesterday, and it's not the first time. I think this should be given some amount of priority. Moving to Medium and M3. We may need another owner for this, I'll ask for volunteers if needed. 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. 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? 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. 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. Switching to P1 due to popular demand. 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. Fixed im master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=68a8caa738caa25f313a0bccfd8179cc5584afa5 Verified in 0ffb02eec2beaea27ff0ec9d3d31b0a09e675a4c A kernel module was built and loaded on the target. |