summaryrefslogtreecommitdiff
path: root/documentation/yocto-project-qs/yocto-project-qs.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-01-20 10:13:32 -0800
committerSaul Wold <sgw@linux.intel.com>2011-01-25 11:58:50 -0800
commitbcce31b4952a9cdb553d0d593b8539fe721acff6 (patch)
treedaf39210837c24263f2517d98cb8ce2c032c308e /documentation/yocto-project-qs/yocto-project-qs.xml
parentdc124306b5ac150b1d63febcedaf316137309aa7 (diff)
downloadopenembedded-core-bcce31b4952a9cdb553d0d593b8539fe721acff6.tar.gz
openembedded-core-bcce31b4952a9cdb553d0d593b8539fe721acff6.tar.bz2
openembedded-core-bcce31b4952a9cdb553d0d593b8539fe721acff6.zip
documentation/yocto-project-qs/yocto-project-qs.xml: Updated list introducing pre-built section
The section that introduces the using a pre-built binary section needed more items in the list. I added text for setting up the environment and for starting QEMU. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation/yocto-project-qs/yocto-project-qs.xml')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml11
1 files changed, 9 insertions, 2 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index f52c699c82..7223e0a7b7 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -302,13 +302,14 @@
</mediaobject>
<para>
- For this scenario you need to do three things:
+ For this scenario you need to do several things:
</para>
<itemizedlist>
<listitem>
<para>
- Install the stand-alone Yocto toolchain tarball.
+ Install the stand-alone Yocto toolchain tarball and then set up the
+ environment to emulate the hardware.
</para>
</listitem>
<listitem>
@@ -323,6 +324,12 @@
Download the filesystem image for your target machine's architecture.
</para>
</listitem>
+ <listitem>
+ <para>
+ Start the QEMU emulator.
+ </para>
+ </listitem>
+
</itemizedlist>
<section id='installing-the-toolchain-and-setting-up-the-environment'>