summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs/yocto-project-qs.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-07-15 15:57:51 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-07-21 10:59:23 +0100
commit6c2a07b36ef96ad7ba0b62e57dab7c0e4c84b609 (patch)
tree9f6c0a8497dd070b88f60db9f6da87f6a54f9573 /documentation/yocto-project-qs/yocto-project-qs.xml
parent028a37cf1b1cdc7f2c1aad6df1a665afba84ab6c (diff)
downloadpoky-6c2a07b36ef96ad7ba0b62e57dab7c0e4c84b609.tar.gz
documentation/yocto-project-qs/yocto-project-qs.xml: Various Robert P. J. Day fixes
Three issues pointed out by Robert P. J. Day. 1) Missing text for "This optional GNOME mobile-based UI, which is intended for devices with resolution but restricted size screens ..." I re-wrote this so it makes sense. 2) Scrubbed document for incorrect usage of openSUSE. There were three occurences. 3) Made several changes to the example of using a pre-built image. The arguments to the poky-qemu command did not exist (they were old). I used existing arguments now and I also bolstered up the root filesystem explanation a bit. (From yocto-docs rev: 31b7a97dfd11ff50ee6c554bf8647591021fef72) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs/yocto-project-qs.xml')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml30
1 files changed, 18 insertions, 12 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 07d752c4c1..e59a1a77cd 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -102,8 +102,8 @@
102 <para> 102 <para>
103 Another important Yocto Project feature is the Sato reference User Interface. 103 Another important Yocto Project feature is the Sato reference User Interface.
104 This optional GNOME mobile-based UI, which is intended for devices with 104 This optional GNOME mobile-based UI, which is intended for devices with
105 resolution but restricted size screens, sits neatly on top of a device using the 105 restricted screen sizes, sits neatly on top of a device using the
106 GNOME Mobile Stack providing a well-defined user experience. 106 GNOME Mobile Stack and provides a well-defined user experience.
107 Implemented in its own layer, it makes it clear to developers how they can implement 107 Implemented in its own layer, it makes it clear to developers how they can implement
108 their own UIs on top of Yocto Linux. 108 their own UIs on top of Yocto Linux.
109 </para> 109 </para>
@@ -119,7 +119,7 @@
119 <itemizedlist> 119 <itemizedlist>
120 <listitem> 120 <listitem>
121 <para>A host system running a supported Linux distribution (i.e. recent releases of 121 <para>A host system running a supported Linux distribution (i.e. recent releases of
122 Fedora, OpenSUSE, Debian, and Ubuntu). 122 Fedora, openSUSE, Debian, and Ubuntu).
123 <note> 123 <note>
124 For notes about using the Yocto Project on development systems that use 124 For notes about using the Yocto Project on development systems that use
125 older Linux distributions see 125 older Linux distributions see
@@ -145,7 +145,7 @@
145 <itemizedlist> 145 <itemizedlist>
146 <listitem><para>Ubuntu</para></listitem> 146 <listitem><para>Ubuntu</para></listitem>
147 <listitem><para>Fedora</para></listitem> 147 <listitem><para>Fedora</para></listitem>
148 <listitem><para>OpenSuse</para></listitem> 148 <listitem><para>openSUSE</para></listitem>
149 </itemizedlist> 149 </itemizedlist>
150 </para> 150 </para>
151 <para> 151 <para>
@@ -196,7 +196,7 @@
196 </literallayout> 196 </literallayout>
197 197
198 <para> 198 <para>
199 The packages you need for an RPM-based host like Fedora and OpenSUSE, 199 The packages you need for an RPM-based host like Fedora and openSUSE,
200 respectively, are as follows: 200 respectively, are as follows:
201 </para> 201 </para>
202 202
@@ -471,15 +471,19 @@
471 </para> 471 </para>
472 472
473 <para> 473 <para>
474 Most kernel files have the following form: 474 Most kernel files have one of the following forms:
475 </para> 475 </para>
476 476
477 <literallayout class='monospaced'> 477 <literallayout class='monospaced'>
478 *zImage*qemu&lt;<emphasis>arch</emphasis>&gt;*.bin 478 *zImage-&lt;<emphasis>kernel-rev</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;*.bin
479 vmlinux-&lt;<emphasis>kernel-rev</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;*.bin
479 480
480 Where: 481 Where:
481 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 482 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
482 x86, x86-64, ppc, mips, or arm. 483 x86, x86-64, ppc, mips, or arm.
484
485 &lt;<emphasis>kernel-rev</emphasis>&gt; is the base Linux kernel revision
486 (e.g. 2.6.37).
483 </literallayout> 487 </literallayout>
484 </section> 488 </section>
485 489
@@ -493,7 +497,7 @@
493 </para> 497 </para>
494 498
495 <literallayout class='monospaced'> 499 <literallayout class='monospaced'>
496 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.ext3 500 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.ext3.bz2
497 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.tar.bz2 501 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.tar.bz2
498 502
499 Where: 503 Where:
@@ -542,13 +546,15 @@
542 546
543 <para> 547 <para>
544 Continuing with the example, the following two commands setup the emulation 548 Continuing with the example, the following two commands setup the emulation
545 environment and launch QEMU. 549 environment and launch QEMU.
546 The kernel and filesystem are for a 32-bit target architecture. 550 This example assumes the root filesystem tarball has been downloaded and expanded, and
551 that the kernel and filesystem are for a 32-bit target architecture.
547 </para> 552 </para>
548 553
549 <literallayout class='monospaced'> 554 <literallayout class='monospaced'>
550 $ source /opt/poky/environment-setup-i686-poky-linux 555 $ source /opt/poky/1.0/environment-setup-i686-poky-linux
551 $ poky-qemu qemux86 zImage-2.6.34-qemux86-1.0.bin yocto-image-sdk-qemux86-1.0.rootfs.ext3 556 $ poky-qemu qemux86 bzImage-2.6.37-qemux86-1.0.bin \
557 yocto-image-sato-qemux86-1.0.rootfs.ext3
552 </literallayout> 558 </literallayout>
553 559
554 <para> 560 <para>