<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 2:27 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 3 May 2016, Bruce Ashfield wrote:<br>
<br>
> On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br>
><br>
> oddly, in the current YP kernel dev manual, i don't see the<br>
> phrase "is not set" explained anywhere in the entire doc,<br>
> which is weird since it seems like it would be important.<br>
><br>
> The manuals don't cover the mechanics of how the mainline kernel is<br>
> configured. Just the same way the don't cover the configuration<br>
> language for any number of packages in the system.<br>
<br>
</span> assuming i'm understanding your position, that's where i'm going to<br>
*strongly* disagree. people who work with the mainline kernel in a<br>
non-OE environment don't use kernel config fragment files. period.<br>
AFAIK (and correct me if i'm wrong), .cfg kernel config fragment files<br>
are exclusively an OE/YP thing, so there is no reason for normal<br>
kernel developers to understand how they work.<br></blockquote><div><br></div><div>Nothing about the options is unique configuration fragments. </div><div><br></div><div>We contributed the merge_config script to the mainline kernel ages ago, so the</div><div>rudimentary support for fragments is carried along with all recent kernel</div><div>trees. At the most basic level, it is a concatenation of a bunch of configs, the</div><div>extra processing around features, the audit, etc, are part of what we do in Yocto,</div><div>but the slamming together of the options and feeding them to the kernel</div><div>configuration system .. is not unique. </div><div><br></div><div>kernel developers have their workflow, and they stick to it. There's no attempt</div><div>to change that .. the reason I mention that, is that people working with the </div><div>mainline kernel can use fragments if they like .. but also can happily ignore</div><div>them as well :D</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
knowing how regular kernel configuration works, and how kernel<br>
config fragment files are processed to aid in that process, are two<br>
*entirely* different things, and how those files are processed is,<br>
IMHO, most assuredly the responsibility of the OE/YP docs to explain.<br></blockquote><div><br></div><div>You referenced # is not set ... that has nothing to do with fragments, and works</div><div>the same way if you are manually editing a .config and then re-running make "old config".</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><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>
</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>