From 468c879a9c3a30596cf5137d53bd222610b24b1d Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 4 Nov 2011 16:00:00 -0700
Subject: 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>
---
 .../dev-manual/dev-manual-bsp-appendix.xml         | 34 ++++++++++------------
 1 file changed, 16 insertions(+), 18 deletions(-)

(limited to 'documentation')

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>
 
-- 
cgit v1.1