sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/bsp-guide/bsp.xml: Updated Linux Kernel Configuration section. 

Another round of feedback from Tom Z applied.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This commit is contained in:
Scott Rifenbark 2010-12-17 16:53:59 -08:00 committed by Richard Purdie
parent 1d671c41df
commit 94f7dd2629
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
documentation/bsp-guide/bsp.xml
View File

@ -315,7 +315,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb
<section id='bsp-filelayout-kernel'> <section id='bsp-filelayout-kernel'>
<title>Linux Kernel Configuration</title> <title>Linux Kernel Configuration</title>
<programlisting> <programlisting>
meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-wrs_git.bbappend meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-yocto-stable.bbappend
</programlisting> </programlisting>
<para> <para>
@ -330,21 +330,26 @@ meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-wrs_git.bbappend
directory. directory.
</para> </para>
<para> <para>
Consider a BSP that uses the <filename>linux-yocto-stable_git.bb</filename> kernel, Supppose you use a BSP that uses the <filename>linux-yocto-stable_git.bb</filename> kernel,
which is the preferred kernel to use for developing a new BSP using the Yocto Project. which is the preferred kernel to use for developing a new BSP using the Yocto Project.
In other words, you have selected the kernel in your
<filename>&lt;bsp_name&gt;.conf</filename> file by adding the following statement:
<programlisting>
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-stable"
</programlisting>
You would use the <filename>linux-yocto-stable_git.bbappend</filename> file to append You would use the <filename>linux-yocto-stable_git.bbappend</filename> file to append
specific BSP settings to the kernel, thus configuring the kernel for your particular BSP. specific BSP settings to the kernel, thus configuring the kernel for your particular BSP.
</para> </para>
<para> <para>
Consider an example for the existing "crownbay" BSP. Now take a look at the existing "crownbay" BSP.
The append file used for the "crownbay" BSP is: The append file used is:
<programlisting> <programlisting>
meta-crownbay/recipes-kernel/linux/linux-yocto-stable_git.bbappend meta-crownbay/recipes-kernel/linux/linux-yocto-stable_git.bbappend
</programlisting> </programlisting>
The file contains the following: The file contains the following:
<programlisting> <programlisting>
FILESEXTRAPATHS := "${THISDIR}/${PN}" FILESEXTRAPATHS := "${THISDIR}/${PN}"
COMPATIBLE_MACHINE_crownbay = "cronwbay" COMPATIBLE_MACHINE_crownbay = "crownbay"
KMACHINE_crownbay = "crownbay" KMACHINE_crownbay = "crownbay"
</programlisting> </programlisting>
This append file adds "crownbay" as a compatible machine, This append file adds "crownbay" as a compatible machine,
@ -366,7 +371,7 @@ KMACHINE_crownbay = "crownbay"
For example, suppose you had a set of configuration options in a file called For example, suppose you had a set of configuration options in a file called
<filename>defonfig</filename>. <filename>defonfig</filename>.
If you put that file inside a directory named If you put that file inside a directory named
<filename class='directory'>/linux-yocto-stable_git</filename> and then added <filename class='directory'>/linux-yocto-stable</filename> and then added
a SRC_URI statement such as the following to the append file, those configuration a SRC_URI statement such as the following to the append file, those configuration
options will be picked up and applied when the kernel is built. options will be picked up and applied when the kernel is built.
<programlisting> <programlisting>