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

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>
This commit is contained in:
Scott Rifenbark 2011-07-15 15:57:51 -07:00 committed by Richard Purdie
parent 028a37cf1b
commit 6c2a07b36e
1 changed files with 18 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -102,8 +102,8 @@
<para> <para>
Another important Yocto Project feature is the Sato reference User Interface. Another important Yocto Project feature is the Sato reference User Interface.
This optional GNOME mobile-based UI, which is intended for devices with This optional GNOME mobile-based UI, which is intended for devices with
resolution but restricted size screens, sits neatly on top of a device using the restricted screen sizes, sits neatly on top of a device using the
GNOME Mobile Stack providing a well-defined user experience. GNOME Mobile Stack and provides a well-defined user experience.
Implemented in its own layer, it makes it clear to developers how they can implement Implemented in its own layer, it makes it clear to developers how they can implement
their own UIs on top of Yocto Linux. their own UIs on top of Yocto Linux.
</para> </para>
@ -119,7 +119,7 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>A host system running a supported Linux distribution (i.e. recent releases of <para>A host system running a supported Linux distribution (i.e. recent releases of
Fedora, OpenSUSE, Debian, and Ubuntu). Fedora, openSUSE, Debian, and Ubuntu).
<note> <note>
For notes about using the Yocto Project on development systems that use For notes about using the Yocto Project on development systems that use
older Linux distributions see older Linux distributions see
@ -145,7 +145,7 @@
<itemizedlist> <itemizedlist>
<listitem><para>Ubuntu</para></listitem> <listitem><para>Ubuntu</para></listitem>
<listitem><para>Fedora</para></listitem> <listitem><para>Fedora</para></listitem>
<listitem><para>OpenSuse</para></listitem> <listitem><para>openSUSE</para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
<para> <para>
@ -196,7 +196,7 @@
</literallayout> </literallayout>
<para> <para>
The packages you need for an RPM-based host like Fedora and OpenSUSE, The packages you need for an RPM-based host like Fedora and openSUSE,
respectively, are as follows: respectively, are as follows:
</para> </para>
@ -471,15 +471,19 @@
</para> </para>
<para> <para>
Most kernel files have the following form: Most kernel files have one of the following forms:
</para> </para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
*zImage*qemu&lt;<emphasis>arch</emphasis>&gt;*.bin *zImage-&lt;<emphasis>kernel-rev</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;*.bin
vmlinux-&lt;<emphasis>kernel-rev</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;*.bin
Where: Where:
&lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm. x86, x86-64, ppc, mips, or arm.
&lt;<emphasis>kernel-rev</emphasis>&gt; is the base Linux kernel revision
(e.g. 2.6.37).
</literallayout> </literallayout>
</section> </section>
@ -493,7 +497,7 @@
</para> </para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.ext3 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.ext3.bz2
yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.tar.bz2 yocto-image-&lt;<emphasis>profile</emphasis>&gt;-qemu&lt;<emphasis>arch</emphasis>&gt;.rootfs.tar.bz2
Where: Where:
@ -542,13 +546,15 @@
<para> <para>
Continuing with the example, the following two commands setup the emulation Continuing with the example, the following two commands setup the emulation
environment and launch QEMU. environment and launch QEMU.
The kernel and filesystem are for a 32-bit target architecture. 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.
</para> </para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source /opt/poky/environment-setup-i686-poky-linux $ source /opt/poky/1.0/environment-setup-i686-poky-linux
$ poky-qemu qemux86 zImage-2.6.34-qemux86-1.0.bin yocto-image-sdk-qemux86-1.0.rootfs.ext3 $ poky-qemu qemux86 bzImage-2.6.37-qemux86-1.0.bin \
yocto-image-sato-qemux86-1.0.rootfs.ext3
</literallayout> </literallayout>
<para> <para>