diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-11-04 16:00:00 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-11-08 16:26:32 +0000 |
commit | 468c879a9c3a30596cf5137d53bd222610b24b1d (patch) | |
tree | 291be6bda8fcccb4902f725708fa56fbdd4c1d93 /documentation/dev-manual/dev-manual-bsp-appendix.xml | |
parent | e8f5b17e86818ae6346ed40f0330cb19946ab626 (diff) | |
download | poky-468c879a9c3a30596cf5137d53bd222610b24b1d.tar.gz |
documentation/dev-manual/dev-manual-bsp-appendix.xml: Added footnote
Per Tom Zanussi's suggestion, we added a footnote to the paragraph
instructing the user on build problems for the example. I don't
have clean fonts in the HTML version of the output. I am still working
on figuring that out.
Reported by: Tom Zanussi
(From yocto-docs rev: 30fe7bd239292ed92f76fbc2f1fad62469f7fe9b)
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/dev-manual-bsp-appendix.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-bsp-appendix.xml | 34 |
1 files changed, 16 insertions, 18 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index eecca8ebd4..ed3af67284 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml | |||
@@ -629,6 +629,22 @@ | |||
629 | Insert the device | 629 | Insert the device |
630 | into a bootable USB socket on the target, and power it on. | 630 | into a bootable USB socket on the target, and power it on. |
631 | The system should boot to the Sato graphical desktop. | 631 | The system should boot to the Sato graphical desktop. |
632 | <footnote><para>Because | ||
633 | this new image is not in any way tailored to the system you're | ||
634 | booting it on, which is assumed to be some sort of atom-pc (netbook) system for this | ||
635 | example, it might not be completely functional though it should at least boot to a text | ||
636 | prompt. | ||
637 | Specifically, it might fail to boot into graphics without some tweaking. | ||
638 | If this ends up being the case, a possible next step would be to replace the | ||
639 | <filename>mymachine.conf</filename> | ||
640 | contents with the contents of <filename>atom-pc.conf</filename> and replace | ||
641 | <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename> | ||
642 | in <filename>meta-yocto</filename> and see if it fares any better. | ||
643 | In any case, following the previous steps will give you a buildable image that | ||
644 | will probably boot on most systems. | ||
645 | Getting things working like you want | ||
646 | them to for your hardware will normally require some amount of experimentation with | ||
647 | configuration settings.</para></footnote> | ||
632 | </para> | 648 | </para> |
633 | 649 | ||
634 | <para> | 650 | <para> |
@@ -647,24 +663,6 @@ | |||
647 | also provides some suggestions for things to try if booting fails and produces | 663 | also provides some suggestions for things to try if booting fails and produces |
648 | strange error messages.</note> | 664 | strange error messages.</note> |
649 | </para> | 665 | </para> |
650 | |||
651 | <para> | ||
652 | Because this new image is not in any way tailored to the system you're | ||
653 | booting it on, which is assumed to be some sort of atom-pc (netbook) system for this | ||
654 | example, it might not be completely functional though it should at least boot to a text | ||
655 | prompt. | ||
656 | Specifically, it might fail to boot into graphics without some tweaking. | ||
657 | If this ends up being the case, a possible next step would be to replace the | ||
658 | <filename>mymachine.conf</filename> | ||
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> | ||
661 | in <filename>meta-yocto</filename> and see if it fares any better. | ||
662 | In any case, following the previous steps will give you a buildable image that | ||
663 | will probably boot on most systems. | ||
664 | Getting things working like you want | ||
665 | them to for your hardware will normally require some amount of experimentation with | ||
666 | configuration settings. | ||
667 | </para> | ||
668 | </section> | 666 | </section> |
669 | </appendix> | 667 | </appendix> |
670 | 668 | ||