| Summary: | More reliable external kernel module selection | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | kernel | Assignee: | California Sullivan <california.l.sullivan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bruce.ashfield, tom.zanussi |
| Version: | 1.8 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Paul Eggleton
2015-04-09 15:27:37 UTC
I did some testing on the other option. It seems to work. With no changes to any other recipes, adding MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS = "kernel-module-hello" to the machine conf (with "hello" being the module that hello-mod in yocto-skeleton creates), there was no error reported and the module was not put in the image. After adding PACKAGES = "kernel-module-hello" to the hello-mod_0.1.bb recipe and rebuilding, the module "hello" was added to the image. Documentation updated; see commit 2c51eae23b634cdace5a119ee1a6c8e8ba76dc45 in the yocto-docs repo. |