https://wiki.in-circuit.de/index.php5?title=Build_a_kernel&feed=atom&action=historyBuild a kernel - Revision history2024-03-29T01:17:00ZRevision history for this page on the wikiMediaWiki 1.20.3https://wiki.in-circuit.de/index.php5?title=Build_a_kernel&diff=4048&oldid=prevCGruenig: /* Menu based configuration */2017-01-31T13:43:19Z<p><span dir="auto"><span class="autocomment">Menu based configuration</span></span></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 13:43, 31 January 2017</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 5:</td>
<td colspan="2" class="diff-lineno">Line 5:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Using buildroot, a working kernel is built automaticly the first time, a image is created. If this default isn't configured as needed, buildroot provides the possibility to invoke ''make linux26-menuconfig'' or ''make linux-menuconfig'' in newer versions. Using this interface is preferred over calling the kernel's menuconfig directly, as certain parameters needed for cross compilation and configuration for a different architecture are set automatically. Additionally buildroot is informed about changes on the kernel configuration automatically and will rebuilt the kernel the next time an image is created.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Using buildroot, a working kernel is built automaticly the first time, a image is created. If this default isn't configured as needed, buildroot provides the possibility to invoke ''make linux26-menuconfig'' or ''make linux-menuconfig'' in newer versions. Using this interface is preferred over calling the kernel's menuconfig directly, as certain parameters needed for cross compilation and configuration for a different architecture are set automatically. Additionally buildroot is informed about changes on the kernel configuration automatically and will rebuilt the kernel the next time an image is created.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>[[File:<del class="diffchange diffchange-inline">kernel_menuconfig</del>.png]]</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>[[File:<ins class="diffchange diffchange-inline">Kernel_menuconfig</ins>.png]]</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Modifying drivers and other code ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Modifying drivers and other code ==</div></td></tr>
</table>CGruenighttps://wiki.in-circuit.de/index.php5?title=Build_a_kernel&diff=1956&oldid=prevTBlocher: /* Menu based configuration */2014-03-31T10:46:58Z<p><span dir="auto"><span class="autocomment">Menu based configuration</span></span></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 10:46, 31 March 2014</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 3:</td>
<td colspan="2" class="diff-lineno">Line 3:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Menu based configuration ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Menu based configuration ==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Using buildroot, a working kernel is built automaticly the first time, a image is created. If this default isn't configured as needed, buildroot provides the possibility to invoke ''make linux26-menuconfig''. Using this interface is preferred over calling the kernel's menuconfig directly, as certain parameters needed for cross compilation and configuration for a different architecture are set automatically. Additionally buildroot is informed about changes on the kernel configuration automatically and will rebuilt the kernel the next time an image is created.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Using buildroot, a working kernel is built automaticly the first time, a image is created. If this default isn't configured as needed, buildroot provides the possibility to invoke ''make linux26-menuconfig'' <ins class="diffchange diffchange-inline">or ''make linux-menuconfig'' in newer versions</ins>. Using this interface is preferred over calling the kernel's menuconfig directly, as certain parameters needed for cross compilation and configuration for a different architecture are set automatically. Additionally buildroot is informed about changes on the kernel configuration automatically and will rebuilt the kernel the next time an image is created.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[File:kernel_menuconfig.png]]</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[File:kernel_menuconfig.png]]</div></td></tr>
</table>TBlocherhttps://wiki.in-circuit.de/index.php5?title=Build_a_kernel&diff=1822&oldid=prevRaik at 13:29, 19 December 20132013-12-19T13:29:41Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 13:29, 19 December 2013</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 17:</td>
<td colspan="2" class="diff-lineno">Line 17:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>within the kernel directory before executing make in the buildroot directory.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>within the kernel directory before executing make in the buildroot directory.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>[[Category:Buildroot]]</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>[[Category:Buildroot<ins class="diffchange diffchange-inline">]] [[Category:HowTo</ins>]]</div></td></tr>
</table>Raikhttps://wiki.in-circuit.de/index.php5?title=Build_a_kernel&diff=177&oldid=prevBenjamin: Created page with 'The Linux Kernel is the main part of the operating system, supplying interface to the hardware and for managing and using applications. To fulfill this task, the kernel is highly…'2011-01-20T11:11:26Z<p>Created page with 'The Linux Kernel is the main part of the operating system, supplying interface to the hardware and for managing and using applications. To fulfill this task, the kernel is highly…'</p>
<p><b>New page</b></p><div>The Linux Kernel is the main part of the operating system, supplying interface to the hardware and for managing and using applications. To fulfill this task, the kernel is highly configurable and sometimes even has to be modified to work properly.<br />
<br />
== Menu based configuration ==<br />
<br />
Using buildroot, a working kernel is built automaticly the first time, a image is created. If this default isn't configured as needed, buildroot provides the possibility to invoke ''make linux26-menuconfig''. Using this interface is preferred over calling the kernel's menuconfig directly, as certain parameters needed for cross compilation and configuration for a different architecture are set automatically. Additionally buildroot is informed about changes on the kernel configuration automatically and will rebuilt the kernel the next time an image is created.<br />
<br />
[[File:kernel_menuconfig.png]]<br />
<br />
== Modifying drivers and other code ==<br />
<br />
Some applications as well as a custom board design might require patching the kernel or modifying the source directly. As described in [[Buildroot directories]] you can find the sources of the linux kernel eg. at project_build_arm/adb1000g45/linux-2.6.33.2. These sources can be modified as needed.<br />
<br />
To be able to decide which packages have been built already and which not, buildroot provides a set of so called stamp files. If these are present and untouched for a given package, it won't be built again, as it is assumed to be recent. This fasten up the whole process of creating a new image. But if there are some files in a specific package, eg. the kernel, are modified, buildroot won't built these automatically. To do so the file ''.stamp_configured'' has to be modified, eg by invoking<br />
<br />
touch .stamp_configured<br />
<br />
within the kernel directory before executing make in the buildroot directory.<br />
<br />
[[Category:Buildroot]]</div>Benjamin