<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 9:12 AM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">On Tue, 3 May 2016, Bruce Ashfield wrote:<br>
<br>
><br>
><br>
> On Tue, May 3, 2016 at 6:53 AM, Robert P. J. Day <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br>
><br>
> (actually, working in wind river linux but i suspect the answer will<br>
> be the same.)<br>
><br>
> i've defined a target board and, rather than supplying a full<br>
> "defconfig" file as a starting point for kernel configuration, my BSP<br>
> layer starts by applying a "kernel_baseline.cfg" file which contains<br>
> only a couple hundred settings that i am particularly interested in.<br>
><br>
> so, given that, how can i tell what OE chose as a starting point for<br>
> a .config file before beginning to apply my kernel config fragments?<br>
> i'm poking around in the log files of the build, but i can't seem to<br>
> see where the "configme" process selects a starting point. am i just<br>
> missing the obvious? i want to see the .config file *before* any of my<br>
> fragments are applied.<br>
><br>
><br>
> If you haven't specified a defconfig (in-tree, or in your layer),<br>
> and are only using fragments, then it will be the first fragment.<br>
> There's no logic to go out and find a baseline, since it would<br>
> almost always not be what someone wanted.<br>
<br>
</span> ok, i'm going to ask a few follow-up questions since i clearly don't<br>
totally understand the full kernel configuration process.<br>
<br></blockquote><div><br></div><div>That's because it varies a bit, based on the kernel and options :)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
i have a BSP layer for a target board that first specifies a<br>
"kernel_baseline.cfg" fragment file which contains just those kernel<br>
config settings i want to make sure are set, and that file is just<br>
over 200 lines long. i also drag in a few other *very* short .cfg<br>
files. but in the end, the .config file generated under<br>
.../linux-windriver/4.1-r0/linux-cxii-standard-build/ is almost 2,200<br>
lines long. where did all that extra content come from?<br></blockquote><div><br></div><div><br></div><div>The .config is always the setting for all reachable kernel options. Some</div><div>are set in fragments, or defconfigs, others are the result of 'select' </div><div>and defaults by the kernel itself, etc.</div><div><br></div><div>If you run <span class="">save</span><span class="">defconfig, you can see the non default options that were</span></div><div><span class="">set.</span></div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
i'm assuming (and i could be wrong here) that since i'm using the<br>
line:<br>
<br>
TARGET_SUPPORTED_KTYPES = "standard"<br>
<br>
i'm automatically incorporating "standard"-related content under<br>
.../kernel-meta/ktypes/standard? as in, the files:<br>
<br>
* standard.cfg<br>
* standard.scc<br>
<br>
or am i mistaken? from where comes all that additional content that<br>
ends up in the final .config? is there a record of it in a log file<br>
somewhere?<br></blockquote><div><br></div><div>If you are not supplying a defconfig, and are inheriting the standard </div><div>kernel options, then yes, you'd be getting those fragments as well.</div><div><br></div><div>You can look in the work-shared/ .. kernel-source/.kernel-meta/ directory</div><div>for the meta-series (if using linux-yocto derived kernels), and that will reference</div><div>everything that was used to configure and patch the kernel. If it isn't in there,</div><div>it was a default or select by the kernel itself.</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
couple more kernel config-related questions coming shortly ...<br>
<div class=""><div class="h5"><br>
rday<br>
<br>
--<br>
<br>
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" rel="noreferrer" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" rel="noreferrer" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" rel="noreferrer" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>