]> code.ossystems Code Review - openembedded-core.git/commitdiff
documentation/bsp-guide/bsp.xml: Updated the Hardware Configuration Options section
authorScott Rifenbark <scott.m.rifenbark@intel.com>
Wed, 15 Dec 2010 22:00:11 +0000 (14:00 -0800)
committerRichard Purdie <rpurdie@linux.intel.com>
Tue, 21 Dec 2010 12:49:44 +0000 (12:49 +0000)
I combined the tuning stuff into this section.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
documentation/bsp-guide/bsp.xml

index e59417d1bd9d4eac93ff14e90486548bcdc29760..752cb126081db27cef71dec8a3b94de519c4add2 100644 (file)
@@ -213,7 +213,10 @@ BBFILE_PRIORITY_bsp = "5"
         </section>
 
         <section id="bsp-filelayout-machine">
-            <title>Hardware Configuration Options (meta-&lt;bsp_name&gt;/conf/machine/*.conf)</title>
+            <title>Hardware Configuration Options</title>
+            <programlisting>
+meta-&lt;bsp_name&gt;/conf/machine/*.conf
+            </programlisting>
 
             <para>
                 The machine files bind together all the information contained elsewhere
@@ -232,16 +235,12 @@ BBFILE_PRIORITY_bsp = "5"
             </para>
 
             <para>
-                At least one machine file is required for a Poky BSP layer.
+                At least one machine file is required for a BSP layer.
                 However, you can supply more than one file.
             </para>
-        </section>
-
-        <section id="bsp-filelayout-tune">
-            <title>Hardware Optimization Options (meta-&lt;bsp_name&gt;/conf/machine/include/tune-*.inc)</title>
 
             <para>
-                These files are shared hardware "tuning" definitions and are commonly used to
+                This directory could also contain shared hardware "tuning" definitions that are commonly used to
                 pass specific optimization flags to the compiler. 
                 An example is <filename>tune-atom.inc</filename>:
             </para>