summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/bsp-guide/bsp.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index ea9b0017f3..ba6ad744a2 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -83,7 +83,7 @@ meta-<bsp_name>/conf/layer.conf
83meta-<bsp_name>/conf/machine/*.conf 83meta-<bsp_name>/conf/machine/*.conf
84meta-<bsp_name>/recipes-bsp/* 84meta-<bsp_name>/recipes-bsp/*
85meta-<bsp_name>/recipes-graphics/* 85meta-<bsp_name>/recipes-graphics/*
86meta-<bsp_name>/recipes-kernel/linux/linux-yocto-stable.bbappend 86meta-<bsp_name>/recipes-kernel/linux/linux-yocto_git.bbappend
87 </programlisting> 87 </programlisting>
88 </para> 88 </para>
89 89
@@ -107,7 +107,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/fix_open_max_prepr
107meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/macro_tweak.patch 107meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/macro_tweak.patch
108meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/nodolt.patch 108meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/nodolt.patch
109meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb 109meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb
110meta-crownbay/recipes-kernel/linux/linux-wrs_git.bbappend 110meta-crownbay/recipes-kernel/linux/linux-yocto_git.bbappend
111 </programlisting> 111 </programlisting>
112 </para> 112 </para>
113 113
@@ -315,7 +315,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb
315 <section id='bsp-filelayout-kernel'> 315 <section id='bsp-filelayout-kernel'>
316 <title>Linux Kernel Configuration</title> 316 <title>Linux Kernel Configuration</title>
317 <programlisting> 317 <programlisting>
318meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-yocto-stable.bbappend 318meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-yocto_git.bbappend
319 </programlisting> 319 </programlisting>
320 320
321 <para> 321 <para>
@@ -330,27 +330,27 @@ meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-yocto-stable.bbappend
330 directory. 330 directory.
331 </para> 331 </para>
332 <para> 332 <para>
333 Suppose you use a BSP that uses the <filename>linux-yocto-stable_git.bb</filename> kernel, 333 Suppose you use a BSP that uses the <filename>linux-yocto_git.bb</filename> kernel,
334 which is the preferred kernel to use for developing a new BSP using the Yocto Project. 334 which is the preferred kernel to use for developing a new BSP using the Yocto Project.
335 In other words, you have selected the kernel in your 335 In other words, you have selected the kernel in your
336 <filename>&lt;bsp_name&gt;.conf</filename> file by adding the following statement: 336 <filename>&lt;bsp_name&gt;.conf</filename> file by adding the following statement:
337 <programlisting> 337 <programlisting>
338PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-stable" 338PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
339 </programlisting> 339 </programlisting>
340 You would use the <filename>linux-yocto-stable_git.bbappend</filename> file to append 340 You would use the <filename>linux-yocto_git.bbappend</filename> file to append
341 specific BSP settings to the kernel, thus configuring the kernel for your particular BSP. 341 specific BSP settings to the kernel, thus configuring the kernel for your particular BSP.
342 </para> 342 </para>
343 <para> 343 <para>
344 Now take a look at the existing "crownbay" BSP. 344 Now take a look at the existing "crownbay" BSP.
345 The append file used is: 345 The append file used is:
346 <programlisting> 346 <programlisting>
347meta-crownbay/recipes-kernel/linux/linux-yocto-stable_git.bbappend 347meta-crownbay/recipes-kernel/linux/linux-yocto_git.bbappend
348 </programlisting> 348 </programlisting>
349 The file contains the following: 349 The file contains the following:
350 <programlisting> 350 <programlisting>
351FILESEXTRAPATHS := "${THISDIR}/${PN}" 351FILESEXTRAPATHS := "${THISDIR}/${PN}"
352COMPATIBLE_MACHINE_crownbay = "crownbay" 352COMPATIBLE_MACHINE_crownbay = "crownbay"
353KMACHINE_crownbay = "crownbay" 353KMACHINE_crownbay = "yocto/standard/crownbay"
354 </programlisting> 354 </programlisting>
355 This append file adds "crownbay" as a compatible machine, 355 This append file adds "crownbay" as a compatible machine,
356 and additionally sets a Yocto Kernel-specific variable that identifies the name of the 356 and additionally sets a Yocto Kernel-specific variable that identifies the name of the
@@ -371,7 +371,7 @@ KMACHINE_crownbay = "crownbay"
371 For example, suppose you had a set of configuration options in a file called 371 For example, suppose you had a set of configuration options in a file called
372 <filename>defconfig</filename>. 372 <filename>defconfig</filename>.
373 If you put that file inside a directory named 373 If you put that file inside a directory named
374 <filename class='directory'>/linux-yocto-stable</filename> and then added 374 <filename class='directory'>/linux-yocto</filename> and then added
375 a SRC_URI statement such as the following to the append file, those configuration 375 a SRC_URI statement such as the following to the append file, those configuration
376 options will be picked up and applied when the kernel is built. 376 options will be picked up and applied when the kernel is built.
377 <programlisting> 377 <programlisting>
@@ -397,7 +397,7 @@ SRC_URI += "file://defconfig \
397 <note><para> 397 <note><para>
398 Other methods exist to accomplish grouping and defining configuration options. 398 Other methods exist to accomplish grouping and defining configuration options.
399 For example, you could directly add configuration options to the Yocto kernel 399 For example, you could directly add configuration options to the Yocto kernel
400 <filename class='directory'>wrs_meta</filename> branch for your BSP. 400 <filename class='directory'>meta</filename> branch for your BSP.
401 The configuration options will likely end up in that location anyway if the BSP gets 401 The configuration options will likely end up in that location anyway if the BSP gets
402 added to the Yocto Project. 402 added to the Yocto Project.
403 For information on how to add these configurations directly, see the 403 For information on how to add these configurations directly, see the
@@ -407,7 +407,7 @@ SRC_URI += "file://defconfig \
407 </para> 407 </para>
408 <para> 408 <para>
409 In general, however, the Yocto Project maintainers take care of moving the SRC_URI-specified 409 In general, however, the Yocto Project maintainers take care of moving the SRC_URI-specified
410 configuration options to the <filename class='directory'>wrs_meta</filename> branch. 410 configuration options to the <filename class='directory'>meta</filename> branch.
411 Not only is it easier for BSP developers to not have to worry about putting those 411 Not only is it easier for BSP developers to not have to worry about putting those
412 configurations in the branch, but having the maintainers do it allows them to apply 412 configurations in the branch, but having the maintainers do it allows them to apply
413 'global' knowledge about the kinds of common configuration options multiple BSPs in 413 'global' knowledge about the kinds of common configuration options multiple BSPs in