From c3ac09f06e7af1bdaedc4bf6daf1c4019a1979e6 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 17 Jun 2015 06:53:11 -0600 Subject: kernel-dev: Added 'make defconfig' details for own source work I added some detail about what really happens when you use the 'make defconfig' command when working with your own sources. Fixes [YOCTO #6611] (From yocto-docs rev: 653c7726e024dcaa908127f0df1d1856f26f4ff0) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'documentation/kernel-dev/kernel-dev-common.xml') diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 532e2e87a6..27c82ceb58 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -646,7 +646,18 @@ files directory as "defconfig" and then add it to the SRC_URI - variable in the recipe. + variable in the recipe. + Running the make defconfig + command results in the default configuration for your + architecture as defined by your kernel. + However, no guarantee exists that this configuration is + valid for your use case, or that your board will even boot. + This is particularly true for non-x86 architectures. + To use non-x86 defconfig files, you + need to be more specific and find one that matches your + board (i.e. for arm, you look in + arch/arm/configs and use the one that + is the best starting point for your board). Edit the following variables in your recipe as appropriate for your project: -- cgit v1.2.3-54-g00ecf