path: root/meta-skeleton/recipes-kernel
AgeCommit message (Collapse)AuthorFilesLines add RPROVIDESJuro Bystricky1-0/+2
Although the package will get an automatic prefix "kernel-module", so the package kernel-module-hello does exist, populating rootfs can generate an error: - nothing provides kernel-module-hello ... This is quite unfortunate, as this recipe is used as a sample. Adding RPROVIDES_${PN} += "kernel-module-hello" to the recipe fixes the problem. [YOCTO #12641] (From OE-Core rev: ca17a7bbea5f5454da43545d544ff7772d83ac19) Signed-off-by: Juro Bystricky <> Signed-off-by: Richard Purdie <>
2015-10-19linux-yocto-custom: fix typo in Upstream-Status tagRoss Burton1-1/+1
(From OE-Core rev: cb46e70148c4210071299acc648c10f1c87cd3fd) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-10-01linux-yocto-custom: Update for newer kernelSaul Wold2-17/+19
Update the NAME version tweak example patch for the newer kernel. This moves the example to the 4.2 stable kernel and appends -custom to the VERSION string. (From OE-Core rev: dc26472661bdc0ed4248d7ab462a296f3c86c421) Signed-off-by: Saul Wold <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-08-24hello-mod: drop PV and PRPaul Eggleton1-3/+0
* PR = "r0" is the default, no need to set it (and most people won't need to set it anyway with the PR service) * PV = "0.1" is already set by virtue of 0.1 being in the filename (From OE-Core rev: 91b323526427f67a8982c7b090e505aaf810d4e7) Signed-off-by: Paul Eggleton <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-05-24linux-yocto-custom: clarify bbappend versus copy in commentsBruce Ashfield1-5/+5
The kernel development manual recommends making a copy of linux-yocto-custom, while the comments in the recipe talk about bbappends. To synchronize the two, we remove the bbappend references from the recipe and instead indicate that a copy should be updated. [YOCTO: #6925] (From OE-Core rev: 121498714b03339d2e5090c2a8fe0618bbaa8610) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2015-03-25skeleton: clarify linux-yocto-custom workflowBruce Ashfield1-4/+2
It was pointed out that the kernel development documentation recommends making a copy of linux-yocto-custom, while the comments in the recipe itself suggest a bbappend. To keep things consistent between these two sources, we update the comment in the recipe itself to also recommend a copy (and rename). [YOCTO: #6925] (From OE-Core rev: aabd47e46a31b526ee880dfd22a1a1f2831ab355) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2014-05-06linux-yocto-custom: provide defconfig guidanceBruce Ashfield1-0/+10
As reported by Andrea, defconfigs created with savedefconfig should specify their expansion mode as "--alldefconfig' for custom yocto recipes. To ensure that this is documented, we can add a comment in the skeleton recipe. Reported-by: Andrea Adami <> (From OE-Core rev: 2c41a28c9a9772531dcfc7079604ff2441c71f8f) Signed-off-by: Bruce Ashfield <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2014-03-27meta-skeleton: Add name attribute to SRC_URIJukka Rissanen1-1/+1
The SRCREV_machine line does not work without having name=machine attribute in SRC_URI. This error is seen if the custom kernel recipe is used without the name attribute: NOTE: Error during finalise of .../ ERROR: ExpansionError during parsing .../ Failure expanding variable do_patch: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure for URL: 'git://;protocol=git;nocheckout=1'. Please set a valid SRCREV for url ['SRCREV_default_pn-linux-yocto-custom', 'SRCREV_default', 'SRCREV_pn-linux-yocto-custom', 'SRCREV'] (possible key names are git://;protocol=git;nocheckout=1, or use a ;rev=X URL parameter) (From OE-Core rev: 760ae021fe1714d04c34bc00d472e2d756b3823a) Signed-off-by: Jukka Rissanen <> Signed-off-by: Richard Purdie <>
2014-03-17linux-yocto-custom: Use SRCREV_machineDarren Hart1-1/+1
The Yocto kernel tools look for SRCREV_machine in do_validate_branches, if it's empty, it just returns and silently continues. This likely needs at least a warning. However, this recipe should be using SRCREV_machine, and not just SRCREV. (From OE-Core rev: f36de92551c8c44a15f1997e65cd8ee957143d95) Signed-off-by: Darren Hart <> Reported-by: Saul Wold <> Cc: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton1-1/+1
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2013-08-20hello-mod: Add comment for kernel module package namingYang Shi1-0/+3
modules bbclass renames kernel module packages with "kernel-module-" prefix automatically. (From OE-Core rev: 6640f312062ad6648459f0b75086e9a8614300a9) Signed-off-by: Yang Shi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-08-20Revert "hello-mod: Ensure the produced package name begins with kernel-module-"Yang Shi1-8/+0
[YOCTO #4286] The package runtime mapping rename issue is already fixed by commit 0bc564af07c1bae8112f834a60aea3b72af7de13, the "kernel-module-" workaround is not necessary anymore for out-of-tree module package, so revert that commit. This reverts commit 71aafc214fe407b7620e747c11dfb8326c867b1c. (From OE-Core rev: b0676d2ffceec3027aee8d2d450ae6318085341e) Signed-off-by: Yang Shi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-04-13hello-mod: Ensure the produced package name begins with kernel-module-Mark Hatle1-0/+8
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example: local.conf: IMAGE_INSTALL_append = " hello-mod" bitbake lib32-core-image-minimal The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-. (From OE-Core rev: b847f87f4213db917d6760cd399c0afae996cf23) Signed-off-by: Mark Hatle <> Signed-off-by: Richard Purdie <>
2012-10-03linux-yocto-custom: Clarify defconfig usageDarren Hart1-1/+2
It is necessary to supply file://defconfig to the SRC_URI when using a defconfig (it is not implicitly understood as the commentary might currently suggest). (From OE-Core rev: 3e244e0e9c10438c2236e56b3de664d4560791f0) Signed-off-by: Darren Hart <> CC: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2012-08-07linux-yocto-custom: Clarify usage and clear COMPATIBLE_MACHINEDarren Hart1-17/+36
There has been some confusion over proper use of the linux-yocto-custom recipe. It is not intended to build as is from meta-skeleton. It should be modified via a bbappend file to provide a Linux kernel config at the very least. Update the commentary to make this requirement more explicit. Add some additional detail about how to create a bbappend file and how and when to modify the various variables. Clear COMPATIBLE_MACHINE so bitbake will not attempt to build the recipe unless the user explicitly adds there machine to the variable, which should encourage them to read the recipe comments before attempting to build it. (From OE-Core rev: 8ac3d0566e793777ec4f6629ef752d6db6231ca9) Signed-off-by: Darren Hart <> CC: Bruce Ashfield <> CC: Tom Zanussi <> Signed-off-by: Darren Hart <> Signed-off-by: Richard Purdie <>
2012-07-03linux-yocto-custom: Remove linux-toolsDarren Hart1-2/+0
Remove the linux-tools include as perf is now packaged independently. Without this, including meta-skeleton in bblayers.conf results in a build failure as cannot be found. (From OE-Core rev: 9d27daeafcc6ea892dee0ee5d0816069b04f6771) Signed-off-by: Darren Hart <> Acked-by: Bruce Ashfield <> CC: Tom Zanussi <> Signed-off-by: Richard Purdie <>
2012-06-18meta-skeleton: add linux-yocto-custom reference recipeBruce Ashfield4-0/+74
Adding a skeleton/refrence recipe for using a subset of the yocto kernel tools against kernel git repositories. Sample/reference configuration fragments, features and a patch are provided and documented in the recipe. From the recipe itself: Provides an example/minimal kernel recipe that uses the linux-yocto and oe-core kernel classes to apply a subset of yocto kernel management to git managed kernel repositories. Notes: kconfig(s): the kernel must be configured with a defconfig, or via configuration fragment(s). Either of these can be added via bbappend. patches: patches can be merged into to the source git tree itself, added using standard bbappend syntax or controlled via .scc feature descriptions (also via bbappends) example configuration addition: SRC_URI += "file://smp.cfg" example patch addition (for kernel v3.4 only): SRC_URI += "file://0001-linux-version-tweak.patch example feature addition (for kernel v3.4 only): SRC_URI += "file://feature.scc" Warning: Building the sample kernel tree ( without providing any configuration will result in build or boot errors. This is not a bug it is a required element for creating a valid kernel. [YOCTO #2397] (From OE-Core rev: 4b6f29ddb00480896f47d96ea376f3a6f6d8451e) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2012-04-10hello-mod: Move hello-mod from meta to meta-skeletonDarren Hart4-0/+402
Fixes [YOCTO #1501] hello-mod is an example kernel module, and does not provide any real functionality. As such, it would be better placed under meta-skeleton than meta. (From OE-Core rev: bde1744018afd4616e114b20ffdc21b9abddcedc) Signed-off-by: Darren Hart <> Signed-off-by: Richard Purdie <>