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 | |
| parent | e8f5b17e86818ae6346ed40f0330cb19946ab626 (diff) | |
| download | ast2050-yocto-poky-468c879a9c3a30596cf5137d53bd222610b24b1d.zip ast2050-yocto-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')
| -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 eecca8e..ed3af67 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -629,6 +629,22 @@ Insert the device into a bootable USB socket on the target, and power it on. The system should boot to the Sato graphical desktop. + <footnote><para>Because + this new image is not in any way tailored to the system you're + booting it on, which is assumed to be some sort of atom-pc (netbook) system for this + example, it might not be completely functional though it should at least boot to a text + prompt. + Specifically, it might fail to boot into graphics without some tweaking. + If this ends up being the case, a possible next step would be to replace the + <filename>mymachine.conf</filename> + contents with the contents of <filename>atom-pc.conf</filename> and replace + <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename> + in <filename>meta-yocto</filename> and see if it fares any better. + In any case, following the previous steps will give you a buildable image that + will probably boot on most systems. + Getting things working like you want + them to for your hardware will normally require some amount of experimentation with + configuration settings.</para></footnote> </para> <para> @@ -647,24 +663,6 @@ also provides some suggestions for things to try if booting fails and produces strange error messages.</note> </para> - - <para> - Because this new image is not in any way tailored to the system you're - booting it on, which is assumed to be some sort of atom-pc (netbook) system for this - example, it might not be completely functional though it should at least boot to a text - prompt. - Specifically, it might fail to boot into graphics without some tweaking. - If this ends up being the case, a possible next step would be to replace the - <filename>mymachine.conf</filename> - contents with the contents of <filename>atom-pc.conf</filename> and replace - <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename> - in <filename>meta-yocto</filename> and see if it fares any better. - In any case, following the previous steps will give you a buildable image that - will probably boot on most systems. - Getting things working like you want - them to for your hardware will normally require some amount of experimentation with - configuration settings. - </para> </section> </appendix> |
