Nothing major, just some simple cleanup in the QS Guide.
Signed-off-by: Robert P. J. Day <[email protected]>
---
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml
b/documentation/yocto-project-qs/yocto-project-qs.xml
index 0f2ecf4..b3e7595 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -6,7 +6,7 @@
<section id='fake-title'>
<title>Yocto Project Quick Start</title>
- <para>Copyright © 2010-2011 Linux Foundation</para>
+ <para>Copyright © 2010-2012 Linux Foundation</para>
</section>
<section id='welcome'>
@@ -34,7 +34,7 @@
rich Yocto Project Development Community into which you can tap.
</para>
<para>
- Finally, you might find the Frequently Asked Questions (FAQ) for the
Yocto Project
+ Finally, you can find the Frequently Asked Questions (FAQ) for the
Yocto Project
at <ulink url='https://wiki.yoctoproject.org/wiki/FAQ'>Yocto Project
FAQ</ulink> and
the FAQ appendix located in
<ulink
url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'>
@@ -470,8 +470,8 @@
</para>
<itemizedlist>
- <listitem><para>Install the stand-alone Yocto toolchain
tarball.</para></listitem>
- <listitem><para>Download the pre-built image that will boot with
QEMU.
+ <listitem><para>Install the appropriate stand-alone Yocto
toolchain tarball.</para></listitem>
+ <listitem><para>Download the pre-built kernel image that will boot
with QEMU.
You need to be sure to get the QEMU image that matches your
target machine’s
architecture (e.g. x86, ARM, etc.).</para></listitem>
<listitem><para>Download the filesystem image for your target
machine's architecture.
@@ -487,7 +487,7 @@
script and support files, from the appropriate directory under
<ulink
url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/toolchain/'></ulink>.
Toolchains are available for 32-bit and 64-bit development
systems from the
- <filename>i686</filename> and <filename>x86_64</filename>
directories, respectively.
+ <filename>i686</filename> and <filename>x86-64</filename>
directories, respectively.
Each type of development system supports five target
architectures.
The tarball files are named such that a string representing
the host system appears
first in the filename and then is immediately followed by a
string representing
@@ -495,7 +495,7 @@
</para>
<literallayout class='monospaced'>
-
poky-eglibc<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.tar.bz2
+
poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.tar.bz2
Where:
<<emphasis>host_system</emphasis>> is a string representing
your development system:
@@ -548,7 +548,7 @@
Be sure to use the kernel that matches the architecture you
want to simulate.
Download areas exist for the five supported machine
architectures:
<filename>qemuarm</filename>, <filename>qemumips</filename>,
<filename>qemuppc</filename>,
- <filename>qemux86</filename>, and
<filename>qemux86_64</filename>.
+ <filename>qemux86</filename>, and
<filename>qemux86-64</filename>.
</para>
<para>
@@ -639,13 +639,13 @@
</para>
<para>
- Continuing with the example, the following two commands setup
the emulation
+ Continuing with the example, the following two commands set up
the emulation
environment and launch QEMU.
This example assumes the root filesystem tarball has been
downloaded and expanded, and
that the kernel and filesystem are for a 32-bit target
architecture.
<literallayout class='monospaced'>
$ source /opt/poky/1.1/environment-setup-i686-poky-linux
- $ runqemu qemux86 bzImage-3.0-qemux86-1.1.bin \
+ $ runqemu qemux86 bzImage-qemux86.bin \
core-image-sato-qemux86.ext3
</literallayout>
</para>
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto