summaryrefslogtreecommitdiffstats
path: root/handbook
diff options
context:
space:
mode:
authorYu Ke <ke.yu@intel.com>2010-09-09 10:34:34 +0800
committerRichard Purdie <rpurdie@linux.intel.com>2010-09-10 12:32:13 +0100
commit0a217cd18f09c837f67bf54956904a79fb013876 (patch)
treec080173ebcb98034b1809b17b092102ffbab9908 /handbook
parent8627258ac3bae635c2ff54cfa24863e50a2a136c (diff)
downloadopenembedded-core-0a217cd18f09c837f67bf54956904a79fb013876.tar.gz
handbook: review and update CH1(introduction) and CH2(using Poky)
Signed-off-by: Yu Ke <ke.yu@intel.com> Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'handbook')
-rw-r--r--handbook/introduction.xml23
-rw-r--r--handbook/usingpoky.xml16
2 files changed, 28 insertions, 11 deletions
diff --git a/handbook/introduction.xml b/handbook/introduction.xml
index 27427c97fa..95017c6a5b 100644
--- a/handbook/introduction.xml
+++ b/handbook/introduction.xml
@@ -30,7 +30,7 @@
<para>Create a focused, stable, subset of OpenEmbedded that can be easily and reliably built and developed upon.</para>
</listitem>
<listitem>
- <para>Fully support a wide range of x86 and ARM hardware and device virtulisation</para>
+ <para>Fully support a wide range of x86, ARM, MIPS, PowerPC hardware and device virtulisation</para>
</listitem>
</itemizedlist>
@@ -39,7 +39,7 @@
based on open source software such as the Kdrive X server, the Matchbox
window manager, the GTK+ toolkit and the D-Bus message bus system. Images
for many kinds of devices can be generated, however the standard example
- machines target QEMU full system emulation (both x86 and ARM) and the ARM based
+ machines target QEMU full system emulation(x86, ARM, MIPS and PowerPC) and the ARM based
Sharp Zaurus series of devices. Poky's ability to boot inside a QEMU
emulator makes it particularly suitable as a test platform for development
of embedded software.
@@ -83,7 +83,11 @@
of the components that make up Poky followed by information about using and
debugging the Poky build system. The <link linkend='extendpoky'>'Extending Poky' section</link>
gives information about how to extend and customise Poky along with advice
- on how to manage these changes. The <link linkend='platdev'>'Platform Development with Poky'
+ on how to manage these changes.
+ The <link linkend='bsp'>'Board Support Packages (BSP) - Developers Guide' section</link>
+ gives information about how to develop BSP such as the common layout, the
+ software hardware configuration options etc.
+ The <link linkend='platdev'>'Platform Development with Poky'
section</link> gives information about interaction between Poky and target
hardware for common platform development tasks such as software development,
debugging and profiling. The rest of the manual
@@ -92,7 +96,7 @@
</para>
<para>
- This manual applies to Poky Release 3.1 (Pinky).
+ This manual applies to Poky Release 3.3 (Green).
</para>
</section>
@@ -200,13 +204,14 @@ $ tar xjvf poky-green-3.3.tar.bz2
$ cd green-3.3/
$ source poky-init-build-env
$ bitbake poky-image-sato
+$ bitbake qemu-native
$ runqemu qemux86
</literallayout>
</para>
<note>
<para>
- This process will need Internet access, about 3 GB of disk space
+ This process will need Internet access, about 20 GB of disk space
available, and you should expect the build to take about 4 - 5 hours since
it is building an entire Linux system from source including the toolchain!
</para>
@@ -266,8 +271,8 @@ $ apt-get install qemu poky-scripts
Download a Poky QEMU release kernel (*zImage*qemu*.bin) and compressed
filesystem image (poky-image-*-qemu*.ext2.bz2) which
you'll need to decompress with 'bzip2 -d'. These are available from the
- <ulink url='http://pokylinux.org/releases/blinky-3.0/'>last release</ulink>
- or from the <ulink url='http://pokylinux.org/autobuild/poky/'>autobuilder</ulink>.
+ <ulink url='http://pokylinux.org/releases/green-3.3/'>last release</ulink>
+ or from the <ulink url='http://autobuilder.pokylinux.org/'>autobuilder</ulink>.
</para>
</listitem>
<listitem>
@@ -306,7 +311,7 @@ $ poky-qemu &lt;kernel&gt; &lt;image&gt;
<para>
We make nightly builds of Poky for testing purposes and to make the
latest developments available. The output from these builds is available
- at <ulink url='http://pokylinux.org/autobuild/'/>
+ at <ulink url='http://autobuilder.pokylinux.org/'/>
where the numbers increase for each subsequent build and can be used to reference it.
</para>
@@ -316,7 +321,7 @@ $ poky-qemu &lt;kernel&gt; &lt;image&gt;
be used either as external standalone toolchains or can be combined with Poky as a
prebuilt toolchain to reduce build time. Using the external toolchains is simply a
case of untarring the tarball into the root of your system (it only creates files in
- <filename class="directory">/usr/local/poky</filename>) and then enabling the option
+ <filename class="directory">/opt/poky</filename>) and then enabling the option
in <filename>local.conf</filename>.
</para>
diff --git a/handbook/usingpoky.xml b/handbook/usingpoky.xml
index 07b8f6c939..50816c9273 100644
--- a/handbook/usingpoky.xml
+++ b/handbook/usingpoky.xml
@@ -118,15 +118,23 @@
</para>
<para>
<literallayout class='monospaced'>
-$ source poky-init-build-env
+$ source poky-init-build-env [build_dir]
</literallayout>
</para>
<para>
+ The build_dir is the dir containing all the building object files. The default
+ build dir is poky-dir/build. Multiple build_dir can be used for different targets.
+ For example, ~/build/x86 for qemux86 target, and ~/build/arm for qemuarm target.
+ Please refer to <link linkend="structure-core-script">poky-init-build-env</link>
+ for detail info
+ </para>
+ <para>
Once the Poky build environment is set up, a target can now be built using:
</para>
<para>
<literallayout class='monospaced'>
$ bitbake &lt;target&gt;
+$ bitbake qemu-native
</literallayout>
</para>
<para>
@@ -135,6 +143,8 @@ $ bitbake &lt;target&gt;
or the name of a recipe for a specific piece of software like
<application>busybox</application>. More details about the standard images
are available in the <link linkend='ref-images'>image reference section</link>.
+ The qemu-native target will build the poky customized qemu, and will be used
+ by runqemu script later.
</para>
</section>
@@ -301,7 +311,7 @@ route add default gw 192.168.0.202 usb0
<para>
You can view a list of tasks in a given package by running
the listtasks task e.g. <command>bitbake matchbox-desktop -c
- listtasks</command>.
+ listtasks</command>, and the result is in file ${WORKDIR}/temp/log.do_listtasks.pid.
</para>
</section>
@@ -317,6 +327,8 @@ route add default gw 192.168.0.202 usb0
directory. They show
which packages and tasks depend on which other packages and
tasks and are useful for debugging purposes.
+ <command>"bitbake -g -u depexp targetname"</command> will show result
+ in more human-readable GUI style.
</para>
</section>