diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2010-12-17 16:53:59 -0800 |
|---|---|---|
| committer |   Richard Purdie <rpurdie@linux.intel.com> | 2010-12-21 12:49:46 +0000 |
| commit | 94f7dd262985b40a6927ea2ed4818307fd9127ab (patch) | |
| tree | 96c9c7f11ec0cb9770366e184abe5459c59f9de3 /documentation | |
| parent | 1d671c41df95be586df0386b3041a68d0e8ae8b4 (diff) | |
| download | openembedded-core-contrib-94f7dd262985b40a6927ea2ed4818307fd9127ab.tar.gz | |
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>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/bsp-guide/bsp.xml | 17 |
1 files changed, 11 insertions, 6 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 7909bb5ba0..e2c9487452 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -315,7 +315,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb <section id='bsp-filelayout-kernel'> <title>Linux Kernel Configuration</title> <programlisting> -meta-<bsp_name>/recipes-kernel/linux/linux-wrs_git.bbappend +meta-<bsp_name>/recipes-kernel/linux/linux-yocto-stable.bbappend </programlisting> <para> @@ -330,21 +330,26 @@ meta-<bsp_name>/recipes-kernel/linux/linux-wrs_git.bbappend directory. </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. + In other words, you have selected the kernel in your + <filename><bsp_name>.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 specific BSP settings to the kernel, thus configuring the kernel for your particular BSP. </para> <para> - Consider an example for the existing "crownbay" BSP. - The append file used for the "crownbay" BSP is: + Now take a look at the existing "crownbay" BSP. + The append file used is: <programlisting> meta-crownbay/recipes-kernel/linux/linux-yocto-stable_git.bbappend </programlisting> The file contains the following: <programlisting> FILESEXTRAPATHS := "${THISDIR}/${PN}" -COMPATIBLE_MACHINE_crownbay = "cronwbay" +COMPATIBLE_MACHINE_crownbay = "crownbay" KMACHINE_crownbay = "crownbay" </programlisting> 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 <filename>defonfig</filename>. 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 options will be picked up and applied when the kernel is built. <programlisting> |