public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/6] linux-yocto-custom: provide defconfig guidance
Date: Mon, 5 May 2014 10:10:08 -0400	[thread overview]
Message-ID: <09e275e174b670b511ee001ea7ef91077a0781df.1399297986.git.bruce.ashfield@windriver.com> (raw)
In-Reply-To: <cover.1399297986.git.bruce.ashfield@windriver.com>

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 <andrea.adami@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
index c3291064bb15..b1a0784c1b7d 100644
--- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
+++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
@@ -32,6 +32,16 @@
 #   patches: patches can be merged into to the source git tree itself,
 #            added via the SRC_URI, or controlled via a BSP
 #            configuration.
+#
+#   defconfig: When a defconfig is provided, the linux-yocto configuration
+#              uses the filename as a trigger to use a 'allnoconfig' baseline
+#              before merging the defconfig into the build. 
+#
+#              If the defconfig file was created with make_savedefconfig, 
+#              not all options are specified, and should be restored with their
+#              defaults, not set to 'n'. To properly expand a defconfig like
+#              this, specify: KCONFIG_MODE="--alldefconfig" in the kernel
+#              recipe.
 #   
 #   example configuration addition:
 #            SRC_URI += "file://smp.cfg"
-- 
1.8.1.2



  parent reply	other threads:[~2014-05-05 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 14:10 [PATCH 0/6] linux-yocto: consolidated pull request Bruce Ashfield
2014-05-05 14:10 ` [PATCH 1/6] kernel-yocto: quote kconfig mode check Bruce Ashfield
2014-05-05 14:10 ` Bruce Ashfield [this message]
2014-05-05 14:10 ` [PATCH 3/6] linux-yocto/3.4: update to v3.4.88 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 4/6] linux-yocto/3.10: update to v3.10.38 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 5/6] linux-yocto/3.14: update to v3.14.2 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 6/6] linux-yocto/3.10: mei.cfg: enable Intel chipsets Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09e275e174b670b511ee001ea7ef91077a0781df.1399297986.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox