summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/bsp-guide/bsp.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index e2c9487452..f5fd217e8a 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -260,7 +260,7 @@ TARGET_CC_ARCH = "-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse"
260 files included with Poky itself. 260 files included with Poky itself.
261 </para> 261 </para>
262 <para> 262 <para>
263 Both the base package architecuture file and the tune file are optional for a Poky BSP layer. 263 Both the base package architecture file and the tune file are optional for a Poky BSP layer.
264 </para> 264 </para>
265 </section> 265 </section>
266 266
@@ -330,7 +330,7 @@ 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 Supppose 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-stable_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:
@@ -369,7 +369,7 @@ KMACHINE_crownbay = "crownbay"
369 </para> 369 </para>
370 <para> 370 <para>
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>defonfig</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-stable</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
@@ -381,7 +381,7 @@ SRC_URI += "file://defconfig"
381 <para> 381 <para>
382 As mentioned earlier, you can group related configurations into multiple files and 382 As mentioned earlier, you can group related configurations into multiple files and
383 name them all in the SRC_URI statement as well. 383 name them all in the SRC_URI statement as well.
384 For example, you could group separate configurations specifically for ethernet and graphics 384 For example, you could group separate configurations specifically for Ethernet and graphics
385 into their own files and add those by using a SRC_URI statement like the 385 into their own files and add those by using a SRC_URI statement like the
386 following in your append file: 386 following in your append file:
387 <programlisting> 387 <programlisting>
@@ -409,7 +409,7 @@ SRC_URI += "file://defconfig \
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'>wrs_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 manintainers 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
414 the tree are typically using. 414 the tree are typically using.
415 This allows for promotion of common configurations into common features. 415 This allows for promotion of common configurations into common features.