summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-11-04 14:22:05 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-08 16:26:32 +0000
commite8f5b17e86818ae6346ed40f0330cb19946ab626 (patch)
tree3fdf626dd43fa2b0648a2af7f61e402a13f31846 /documentation/dev-manual
parent02e5570bc1435ce357624a209bc0a584da27b097 (diff)
downloadpoky-e8f5b17e86818ae6346ed40f0330cb19946ab626.tar.gz
documentation/dev-manual/dev-manual-bsp-appendix.xml: Tom Zanussi edits.
Some wording changes to keep things accurate. Also inserted some "&nbsp" characters in some headings to force an extra space between normal font and courier font words. It appears the PDF version of the generated manual shoves these words together with no intervening space. Looks like hell. Reported by: Tom Zanussi (From yocto-docs rev: 5dcb9ae99f1752599fd56a276ccafd79a52334f8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index 987941c87f..eecca8ebd4 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -100,7 +100,7 @@
100 <para> 100 <para>
101 You need to have the base BSP layer on your development system. 101 You need to have the base BSP layer on your development system.
102 Similar to the local Yocto Project files, you can get the BSP 102 Similar to the local Yocto Project files, you can get the BSP
103 layer a couple of different ways: 103 layer in a couple of different ways:
104 download the BSP tarball and extract it, or set up a local Git repository that 104 download the BSP tarball and extract it, or set up a local Git repository that
105 has the Yocto Project BSP layers. 105 has the Yocto Project BSP layers.
106 You should use the same method that you used to get the local Yocto Project files earlier. 106 You should use the same method that you used to get the local Yocto Project files earlier.
@@ -282,7 +282,7 @@
282 </para> 282 </para>
283 283
284 <section id='changing-recipes-bsp'> 284 <section id='changing-recipes-bsp'>
285 <title>Changing <filename>recipes-bsp</filename></title> 285 <title>Changing&nbsp;&nbsp;<filename>recipes-bsp</filename></title>
286 286
287 <para> 287 <para>
288 First, let's look at <filename>recipes-bsp</filename>. 288 First, let's look at <filename>recipes-bsp</filename>.
@@ -299,7 +299,7 @@
299 </section> 299 </section>
300 300
301 <section id='changing-recipes-graphics'> 301 <section id='changing-recipes-graphics'>
302 <title>Changing <filename>recipes-graphics</filename></title> 302 <title>Changing&nbsp;&nbsp;<filename>recipes-graphics</filename></title>
303 303
304 <para> 304 <para>
305 Now let's look at <filename>recipes-graphics</filename>. 305 Now let's look at <filename>recipes-graphics</filename>.
@@ -320,7 +320,7 @@
320 </section> 320 </section>
321 321
322 <section id='changing-recipes-core'> 322 <section id='changing-recipes-core'>
323 <title>Changing <filename>recipes-core</filename></title> 323 <title>Changing&nbsp;&nbsp;<filename>recipes-core</filename></title>
324 324
325 <para> 325 <para>
326 Now let's look at changes in <filename>recipes-core</filename>. 326 Now let's look at changes in <filename>recipes-core</filename>.
@@ -349,7 +349,7 @@
349 </section> 349 </section>
350 350
351 <section id='changing-recipes-kernel'> 351 <section id='changing-recipes-kernel'>
352 <title>Changing <filename>recipes-kernel</filename></title> 352 <title>Changing&nbsp;&nbsp;<filename>recipes-kernel</filename></title>
353 353
354 <para> 354 <para>
355 Finally, let's look at <filename>recipes-kernel</filename> changes. 355 Finally, let's look at <filename>recipes-kernel</filename> changes.
@@ -611,7 +611,7 @@
611 Finally, once you have an image, you can try booting it from a device 611 Finally, once you have an image, you can try booting it from a device
612 (e.g. a USB device). 612 (e.g. a USB device).
613 To prepare a bootable USB device, insert a USB flash drive into your build system and 613 To prepare a bootable USB device, insert a USB flash drive into your build system and
614 copy the <filename>.hddimage</filename>, located in the 614 copy the <filename>.hddimg</filename> file, located in the
615 <filename>poky/build/tmp/deploy/images</filename> 615 <filename>poky/build/tmp/deploy/images</filename>
616 directory after a successful build to the flash drive. 616 directory after a successful build to the flash drive.
617 Assuming the USB flash drive takes device <filename>/dev/sdf</filename>, 617 Assuming the USB flash drive takes device <filename>/dev/sdf</filename>,
@@ -659,8 +659,8 @@
659 contents with the contents of <filename>atom-pc.conf</filename> and replace 659 contents with the contents of <filename>atom-pc.conf</filename> and replace
660 <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename> 660 <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename>
661 in <filename>meta-yocto</filename> and see if it fares any better. 661 in <filename>meta-yocto</filename> and see if it fares any better.
662 In any case, following the previous steps should 662 In any case, following the previous steps will give you a buildable image that
663 probably give you a buildable and bootable image. 663 will probably boot on most systems.
664 Getting things working like you want 664 Getting things working like you want
665 them to for your hardware will normally require some amount of experimentation with 665 them to for your hardware will normally require some amount of experimentation with
666 configuration settings. 666 configuration settings.