documentation/dev-manual/dev-manual-model.xml: removed image description list.

I moved the image description list to the Yocto Project Reference manual
where it really belonged.  Appropriate references were added.

(From yocto-docs rev: fc74439c09d1f45cdfbc24d972045e574ffa91ec)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 12 insertions, 92 deletions

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 016a0f104f..eeb792b370 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -158,56 +158,15 @@
                     Building an Image</ulink> section of the Yocto Project Quick Start.    
                     You might want to reference this information.</para></listitem>
                 <listitem><para><emphasis>Build the image</emphasis>:  The Yocto Project uses the BitBake 
-                    tool to build images based on the type of image 
-                    you want to create.  
+                    tool to build images based on the type of image you want to create.  
                     You can find more information on BitBake 
                     <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
                     <para>The build process supports several types of images to satisfy different needs.  
-                    When you issue the BitBake command you provide a “top-level” recipe that essentially 
-                    starts the process off of building the type of image you want.</para>
-                    <para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>
-                    <para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and 
-                    <filename>meta/recipes-sato/images</filename> directories of your local Yocto Project 
-                    file structure (Git repository or extracted release tarball).  
-                    Although the recipe names are somewhat explanatory, here is a list that describes them:
-                    <itemizedlist>
-                        <listitem><para><emphasis>Base</emphasis> – A foundational basic image without support 
-                            for X that can be reasonably used for customization.</para></listitem>
-                        <listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for 
-                            X that can be reasonably used for customization.</para></listitem>
-                        <listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to 
-                            the disk of the target device.</para></listitem>
-                        <listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from 
-                            a CD without having to first install something.</para></listitem>
-                        <listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.  
-                            This image is not much more than a kernel with a shell.</para></listitem>
-                        <listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for 
-                            development work.</para></listitem>
-                        <listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> – 
-                            A minimal image 
-                           that has the <filename>initramfs</filename> as part of the kernel, which allows the 
-                            system to find the first “init” program more efficiently.</para></listitem>
-                        <listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
-                       <listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support 
-                            for the MTD utilities, which let the user interact with the MTD subsystem in 
-                            the kernel to perform operations on flash devices.</para></listitem>
-                        <listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment 
-                            and visual style that works well with mobile devices.</para></listitem>
-                        <listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for 
-                            development work.</para></listitem>
-                        <listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project 
-                            toolchain and development libraries.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live 
-                           image.</para></listitem>
-                    </itemizedlist>
-                </para></listitem>
+                    See 
+                    <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
+                    Reference: Images</ulink> in the 
+                    <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
+                    Yocto Project Reference Manual</ulink>for information on supported images.</para></listitem>
             </orderedlist>
         </para>
 
@@ -387,51 +346,12 @@
                         You can find more information on BitBake 
                         <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
                         <para>The build process supports several types of images to satisfy different needs.  
-                        When you issue the BitBake command you provide a “top-level” recipe that essentially 
-                        starts the process off of building the type of image you want.</para>
-                        <para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>
-                        <para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and 
-                        <filename>meta/recipes-sato/images</filename> directories of your local Yocto Project 
-                        file structure (Git repository or extracted release tarball).  
-                        Although the recipe names are somewhat explanatory, here is a list that describes them:
-                        <itemizedlist>
-                            <listitem><para><emphasis>Base</emphasis> – A foundational basic image without support 
-                                for X that can be reasonably used for customization.</para></listitem>
-                            <listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for 
-                                X that can be reasonably used for customization.</para></listitem>
-                            <listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to 
-                                the disk of the target device.</para></listitem>
-                            <listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from 
-                                a CD without having to first install something.</para></listitem>
-                            <listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.  
-                                This image is not much more than a kernel with a shell.</para></listitem>
-                            <listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for 
-                                development work.</para></listitem>
-                            <listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> – 
-                                A minimal image 
-                                that has the <filename>initramfs</filename> as part of the kernel, which allows the 
-                                system to find the first “init” program more efficiently.</para></listitem>
-                            <listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
-                            <listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support 
-                                for the MTD utilities, which let the user interact with the MTD subsystem in 
-                                the kernel to perform operations on flash devices.</para></listitem>
-                            <listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment 
-                                and visual style that works well with mobile devices.</para></listitem>
-                            <listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for 
-                                development work.</para></listitem>
-                            <listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project 
-                                toolchain and development libraries.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live 
-                               image.</para></listitem>
-                        </itemizedlist>
-                    </para></listitem>
+                        See 
+                        <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
+                        Reference: Images</ulink> in the 
+                        <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
+                        Yocto Project Reference Manual</ulink> for information on supported 
+                        images.</para></listitem>
                     <listitem><para><emphasis>Make your configuration changes available
                         in the kernel layer</emphasis>:  Up to this point all the configuration changes to the 
                         kernel have been done and tested iteratively.