]> code.ossystems Code Review - openembedded-core.git/commitdiff
documentation/kernel-manual/kernel-concepts.xml: Updated the text so that the concep...
authorScott Rifenbark <scott.m.rifenbark@intel.com>
Mon, 29 Nov 2010 17:26:22 +0000 (09:26 -0800)
committerSaul Wold <Saul.Wold@intel.com>
Sat, 11 Dec 2010 06:01:18 +0000 (22:01 -0800)
Feedback indicated by Dave suggested getting rid of this.  So I commented out the text around it and modified the reminder text so it did not reference a figure.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
documentation/kernel-manual/kernel-concepts.xml

index b884f138e0d41248b9972c939f9018a9ae73741e..872264c8460eba8e0f6dd52bac28dd1d69796988 100644 (file)
             our baseline kernel version.
         </para>
         <para>
+            The ultimate source for the Yocto Project kernel is a released kernel 
+            from kernel.org.
+            In addition to a foundational kernel from kernel.org the commercially released 
+            Yocto Project kernel contains a mix of important new mainline
+            developments, non-mainline developments, Board Support Package (BSP) developments,
+            and custom features.
+            These additions result in a commercially released Yocto Project kernel that caters 
+            to specific embedded designer needs for targeted hardware.
+        </para>
+<!--        <para>
             The following figure represents the overall place the Yocto Project kernel fills.
         </para>
         <para>
             and custom features.
             These additions result in a commercially released Yocto Project kernel that caters 
             to specific embedded designer needs for targeted hardware. 
-        </para>
+        </para> -->
         <para>
             Once a Yocto Project kernel is officially released the Yocto Project team goes into 
             their next development cycle, or "uprev" cycle.
             possible kernel.org version.
             The team continually monitors community kernel
             development to look for significant features of interest.
-            The illustration depicts this by showing the team looking back to kernel.org for new features, 
-            BSP features, and significant bug fixes.
+<!--            The illustration depicts this by showing the team looking back to kernel.org for new features, 
+            BSP features, and significant bug fixes. -->
             The team does consider back-porting large features if they have a significant advantage. 
             User or community demand can also trigger a back-port or creation of new
             functionality in the Yocto Project baseline kernel during the uprev cycle.