sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/yocto-project-qs/yocto-project-qs.xml: Misc. Edits 

I received a patch from Robert P. J. Day that had several changes.
Curiously, several did not apply.  I think that the patch was
applied using a version other than the "latest" version.  In
any case, I applied the changes that did need applied.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 5af725001cf045040f83e1c891385692f8a3a287)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-03-05 16:45:57 -06:00 committed by Richard Purdie
parent b257acf053
commit 1084bc5d77
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@ -476,7 +476,7 @@
</para>
<itemizedlist>
<listitem><para>Install the stand-alone Yocto toolchain tarball.</para></listitem>
<listitem><para>Install the appropriate stand-alone Yocto toolchain tarball.</para></listitem>
<listitem><para>Download the pre-built 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>
@ -493,7 +493,7 @@
script and support files, from the appropriate directory under
<ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></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
@ -501,7 +501,7 @@
</para>
<literallayout class='monospaced'>
poky-eglibc&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;-toolchain-gmae-&lt;<emphasis>release</emphasis>&gt;.tar.bz2
poky-eglibc-&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;-toolchain-gmae-&lt;<emphasis>release</emphasis>&gt;.tar.bz2
Where:
&lt;<emphasis>host_system</emphasis>&gt; is a string representing your development system:
@ -554,7 +554,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>
@ -651,7 +651,7 @@
that the kernel and filesystem are for a 32-bit target architecture.
<literallayout class='monospaced'>
$ source &YOCTO_ADTPATH_DIR;/environment-setup-i686-poky-linux
$ runqemu qemux86 bzImage-3.0-qemux86-&DISTRO;.bin \
$ runqemu qemux86 bzImage-qemux86-&DISTRO;.bin \
core-image-sato-qemux86.ext3
</literallayout>
</para>