From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 28 Sep 2012 17:40:13 +0000 (-0700)
Subject: documentation: dev-manual - Added QEMU for image target.
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0101e9edf47d49bd25632389a735bdc298c4a728;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git

documentation: dev-manual - Added QEMU for image target.

(From yocto-docs rev: 6dceb27dd5687e1a6a9ae3ad8decccbaa211376a)

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

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 96db505d269..a32c31a408a 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -291,8 +291,8 @@
                 Sometimes this toolchain is referred to as the meta-toolchain.</para></listitem>
             <listitem><para><emphasis>Image:</emphasis> An image is the result produced when 
                 BitBake processes a given collection of recipes and related metadata.
-                Images are the binary output that run on specific hardware and for specific
-                use cases.
+                Images are the binary output that run on specific hardware or QEMU 
+                and for specific use cases.
                 For a list of the supported image types that the Yocto Project provides, see the
                 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>"
                 chapter in the Yocto Project Reference Manual.</para></listitem>