summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-08-04 11:43:47 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-15 15:26:59 +0100
commitbfb2c2c6af4fc6cdfa9f4494dda74cec5bedf895 (patch)
tree705ac9cd7ef395c179b548f83c654b87e4fc203d
parent572449b29cfd5af133e64deed9a2537f4f94f232 (diff)
downloadpoky-bfb2c2c6af4fc6cdfa9f4494dda74cec5bedf895.tar.gz
documentation/dev-manual/dev-manual-kernel-appendix.xml: new section for image
I added a new section for the example that ensures the image for qemu is available. (From yocto-docs rev: a3ca52cb7088ec85502b507093082f35f23befd4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-kernel-appendix.xml66
1 files changed, 66 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index 787be3df5d..352924c1f9 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -168,6 +168,72 @@
168 </para> 168 </para>
169 </section> 169 </section>
170 170
171 <section id='be-sure-the-image-is-available'>
172 <title>Be Sure the Image is Available</title>
173
174 <para>
175 For the example you need an image that you can use when you run the QEMU emulator.
176 By default, support of VFAT filesystems will not be supported in this image.
177 The example will test that in a subsequent section.
178 </para>
179
180 <para>
181 In theory, you can get an image suitable for QEMU one of two ways:
182 <itemizedlist>
183 <listitem><para>Download a pre-built kernel image and matching <filename>ext3</filename>
184 file system from the Yocto Project
185 <ulink url='http://autobuilder.yoctoproject.org/downloads/'>Index of downloads</ulink>.
186 See <link linkend='index-downloads'>Index of Downloads</link> earlier in the
187 manual for more information about this source repository.
188 You can also see
189 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#using-pre-built'>
190 Using Pre-Build Binaries and QEMU</ulink>
191 in the Yocto Project Quick Start for information on how to find and choose
192 images ready to run in QEMU.</para></listitem>
193 <listitem><para>Build an image and matching <filename>ext3</filename>
194 filesystem using the <filename>poky</filename> Git repository on your local
195 development system.</para></listitem>
196 </itemizedlist>
197 </para>
198
199 <para>
200 This example continues by building the image.
201 If you want to see more on building an image in general, see
202 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>
203 Building an Image</ulink> in the Yocto Project Quick Start.
204 </para>
205
206 <para>
207 The following steps result in a QEMU image and filesystem for
208 an x86 (32-bit) target machine that can run in the emulator.
209 <orderedlist>
210 <listitem><para><emphasis>Prepare the Build Environment</emphasis> - Source the
211 script to set up the build environment:
212 <literallayout class='monospaced'>
213 $ cd ~/poky
214 $ source oe-init-build-env
215 </literallayout></para></listitem>
216 <listitem><para><emphasis>Change Configurations to Speed Up the Build</emphasis> - If your
217 development system supports multiple cores you can remove the comments in the
218 <filename>BB_NUMBER_THREADS</filename> and <filename>PARALLEL_MAKE</filename>
219 statements and adjust the arguments to optimize the build time.
220 For example, a development host that has four cores could use
221 <filename>8</filename> and <filename>j 6</filename> to get the best use of
222 your host's multi-core and thread capabilities.</para></listitem>
223 <listitem><para><emphasis>Start the Build</emphasis> - Use BitBake to start the
224 build:
225 <literallayout class='monospaced'>
226 $ bitbake -k core-image-sato
227 </literallayout>
228 Depending on your host system's load and capabilities the build takes some time.
229 Once it completes you will have the kernel image needed to continue the example.
230 The image and filesystem reside in the build directory at
231 <filename>poky/build/tmp/deploy/images</filename>.
232 </para></listitem>
233 </orderedlist>
234 </para>
235 </section>
236
171 <section id='prepare-to-use-menuconfig'> 237 <section id='prepare-to-use-menuconfig'>
172 <title>Prepare to use <filename>menuconfig</filename></title> 238 <title>Prepare to use <filename>menuconfig</filename></title>
173 239