<br><br><div class="gmail_quote">On Fri, Jul 6, 2012 at 5:06 PM, Rifenbark, Scott M <span dir="ltr"><<a href="mailto:scott.m.rifenbark@intel.com" target="_blank">scott.m.rifenbark@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Jim,
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I am looking at that section in the BSP Guide and it is actually out of date regarding the 1.2.10 section. In the section it lists the linux-yocto_3.0.bbappend
file (which is probably lagging as it should be 3.2). Anyway, the listing uses KERNEL_FEATURES and I believe that KBRANCH is now used. I am going to work on this section and get it up to speed and then address the issue you originally brought up, which is
getting the best description for config fragments inside the dev manual. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">ScottR<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> </span></p></div></div></blockquote><div>Scott,<br><br>I found out over the weekend that the config fragment file needs to have the .cfg extension. This would agree with the example in the Developer Manual, but make the BSP Guide in error, as it uses no extension. A note to the .cfg requirement would seem to be a required addition.<br>
<br>JIm A<br><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="white" link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal">
<span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> <a href="mailto:yocto-bounces@yoctoproject.org" target="_blank">yocto-bounces@yoctoproject.org</a> [mailto:<a href="mailto:yocto-bounces@yoctoproject.org" target="_blank">yocto-bounces@yoctoproject.org</a>]
<b>On Behalf Of </b>jfabernathy<br>
<b>Sent:</b> Friday, July 06, 2012 11:59 AM<br>
<b>To:</b> <a href="mailto:yocto@yoctoproject.org" target="_blank">yocto@yoctoproject.org</a><br>
<b>Subject:</b> [yocto] Documentation improvement<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I was looking at the Yocto Development Manual (Latest), section 4.6.2. Creating Config Fragments. I was confused about the file statement and the naming of the directory to locate the fragment file until I
found a similar discussion in the BSP Guide (lastest) section 1.2.10. Linux Kernel Configuration.
<br>
<br>
The section there is much more understandable. I think we need to modify the development manual or have it point to the BSP manual. The text from there (below) I think is better. I still think it's confusing about the naming of the subdirectory where the
myconfig goes. Maybe a complete example would be good.<u></u><u></u></p>
<p class="MsoNormal">For example, suppose you had a set of configuration options in a file called
<code><span style="font-size:10.0pt">myconfig</span></code>. If you put that file inside a directory named
<code><span style="font-size:10.0pt">linux-yocto</span></code> and then added a <code>
<span style="font-size:10.0pt">SRC_URI</span></code> statement such as the following to the append file, those configuration options will be picked up and applied when the kernel is built.
<u></u><u></u></p>
<pre> SRC_URI += <a>"file://myconfig"</a><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<p>As mentioned earlier, you can group related configurations into multiple files and name them all in the
<code><span style="font-size:10.0pt">SRC_URI</span></code> statement as well. For example, you could group separate configurations specifically for Ethernet and graphics into their own files and add those by using a
<code><span style="font-size:10.0pt">SRC_URI</span></code> statement like the following in your append file:
<u></u><u></u></p>
<pre> SRC_URI += <a>"file://myconfig \<u></u><u></u></a></pre>
<pre><span><a> file://eth.cfg \<u></u><u></u></a></span></pre>
<pre><span><a> file://gfx.cfg"</a></span><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
</div></div></div>
</div>
</blockquote></div><br>