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).
Signed-off-by: Darren Hart <[email protected]> CC: Bruce Ashfield <[email protected]> --- meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb index 1f0b3a2..4115d2f 100644 --- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb +++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb @@ -13,7 +13,8 @@ # # You must also provide a Linux kernel configuration. The most direct # method is to copy your .config to files/defconfig in your layer, -# in the same directory as the bbappend. +# in the same directory as the bbappend and add file://defconfig to +# your SRC_URI. # # To use the yocto kernel tooling to generate a BSP configuration # using modular configuration fragments, see the yocto-bsp and -- 1.7.11.4 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
