All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: how the &^$%^%@%^#$ does "file://defconfig" work?
Date: Wed, 24 Apr 2013 08:43:53 -0400	[thread overview]
Message-ID: <5177D389.40902@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304240837370.29691@oneiric>

On 13-04-24 08:38 AM, Robert P. J. Day wrote:
> On Wed, 24 Apr 2013, Bruce Ashfield wrote:
>
>> On 13-04-24 07:50 AM, Robert P. J. Day wrote:
>>>
>>>     been fighting with this for a couple of hours, so i'll start with
>>> the short version -- here's the current explanation for "Changing the
>>> Configuration" of your kernel:
>>>
>>> http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration
>>>
>>>     the salient bit:
>>>
>>> "If you have a complete Linux kernel .config file you want to use,
>>> copy it to a directory named files, which must be in your layer's
>>> recipes-kernel/linux directory, and name the file "defconfig"."
>>>
>>>     first, that clearly suggests that file://defconfig is to be used
>>> *only* when you have a complete .config file you want to use, which
>>> also implies that if you use that, you should not be picking up any
>>> other snippets. that's how i read that -- the use of
>>> "file://defconfig" means that that is *exactly* the final form of my
>>> eventual .config file. if that's not true, then that wording needs to
>>> change.
>>>
>>>     also, i've been trying to do just that for a couple hours now, and i
>>> am definitely *not* getting that as my final .config file used for the
>>> kernel configuration. so what should be happening here? thanks.
>>
>> What sort of delta are you seeing ? Just because something is a
>> defconfig, doesn't mean that will be exactly what you see in the final
>> .config.
>>
>> It also could vary a bit based on the kernel recipe you are using,
>> i.e. if there are configure prepends or appends, or any input
>> conditioning.
>>
>> The kernel's configuration routines will take all that input and
>> potentially select, deselect or take defaults for values that are
>> not in the defconfig .. hence why you'll see a delta.
>
>    i'm starting to follow the logic, i think it's just the wording in
> that section that needs tweaking. or maybe i just didn't get enough
> sleep ...

Or maybe both!

Bruce

>
> rday
>



  reply	other threads:[~2013-04-24 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 11:50 how the &^$%^%@%^#$ does "file://defconfig" work? Robert P. J. Day
2013-04-24 12:34 ` Bruce Ashfield
2013-04-24 12:38   ` Robert P. J. Day
2013-04-24 12:43     ` Bruce Ashfield [this message]
2013-04-24 15:36 ` Rifenbark, Scott M

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=5177D389.40902@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.