From patchwork Wed Oct 3 04:36:41 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: linux-yocto-custom: Clarify defconfig usage Date: Wed, 03 Oct 2012 04:36:41 -0000 From: Darren Hart X-Patchwork-Id: 37649 Message-Id: <52507f028d9ec0e88078673e15e238d010cfaead.1349239001.git.dvhart@linux.intel.com> To: openembedded-core@lists.openembedded.org Cc: Darren Hart 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 CC: Bruce Ashfield Acked-by: Bruce Ashfield --- 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