* how the &^$%^%@%^#$ does "file://defconfig" work?
@ 2013-04-24 11:50 Robert P. J. Day
2013-04-24 12:34 ` Bruce Ashfield
2013-04-24 15:36 ` Rifenbark, Scott M
0 siblings, 2 replies; 5+ messages in thread
From: Robert P. J. Day @ 2013-04-24 11:50 UTC (permalink / raw)
To: Yocto discussion list
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.
rday
p.s. as i have some spare time between contracts at the moment, i am
going to be going over some of the yocto docs in excruciating detail.
somewhere, scott rifenbark is now thinking, "oh, crap, ..."
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: how the &^$%^%@%^#$ does "file://defconfig" work?
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 15:36 ` Rifenbark, Scott M
1 sibling, 1 reply; 5+ messages in thread
From: Bruce Ashfield @ 2013-04-24 12:34 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
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.
Cheers,
Bruce
>
> rday
>
> p.s. as i have some spare time between contracts at the moment, i am
> going to be going over some of the yocto docs in excruciating detail.
> somewhere, scott rifenbark is now thinking, "oh, crap, ..."
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how the &^$%^%@%^#$ does "file://defconfig" work?
2013-04-24 12:34 ` Bruce Ashfield
@ 2013-04-24 12:38 ` Robert P. J. Day
2013-04-24 12:43 ` Bruce Ashfield
0 siblings, 1 reply; 5+ messages in thread
From: Robert P. J. Day @ 2013-04-24 12:38 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: Yocto discussion list
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 ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: how the &^$%^%@%^#$ does "file://defconfig" work?
2013-04-24 12:38 ` Robert P. J. Day
@ 2013-04-24 12:43 ` Bruce Ashfield
0 siblings, 0 replies; 5+ messages in thread
From: Bruce Ashfield @ 2013-04-24 12:43 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how the &^$%^%@%^#$ does "file://defconfig" work?
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 15:36 ` Rifenbark, Scott M
1 sibling, 0 replies; 5+ messages in thread
From: Rifenbark, Scott M @ 2013-04-24 15:36 UTC (permalink / raw)
To: Robert P. J. Day, Yocto discussion list
>-----Original Message-----
>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
>Sent: Wednesday, April 24, 2013 4:51 AM
>To: Yocto discussion list
>Subject: [yocto] how the &^$%^%@%^#$ does "file://defconfig" work?
>
>
> 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.
>
>rday
>
>p.s. as i have some spare time between contracts at the moment, i am
>going to be going over some of the yocto docs in excruciating detail.
>somewhere, scott rifenbark is now thinking, "oh, crap, ..."
Your feedback always improves things Robert... no problems.
>
>--
>
>========================================================================
>Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
>Twitter: http://twitter.com/rpjday
>LinkedIn: http://ca.linkedin.com/in/rpjday
>========================================================================
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-04-24 15:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2013-04-24 15:36 ` Rifenbark, Scott M
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.