summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-08-04 15:57:16 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-15 15:26:59 +0100
commitf12904a9224b1e8499cf10aa8366d39dea20ffc9 (patch)
tree6e2727116bc444639f44227723066ae6ce770e2a /documentation
parentbfb2c2c6af4fc6cdfa9f4494dda74cec5bedf895 (diff)
downloadpoky-f12904a9224b1e8499cf10aa8366d39dea20ffc9.tar.gz
documentation/dev-manual/dev-manual-kernel-appendix.xml: partial edits.
still working on the kernel example. (From yocto-docs rev: 90c8cb778d3c146f24626a681f05b88bab1e9766) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-kernel-appendix.xml61
1 files changed, 61 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index 352924c1f9..5aed90f95b 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -234,6 +234,67 @@
234 </para> 234 </para>
235 </section> 235 </section>
236 236
237 <section id='is-vfat-supported'>
238 <title>Is VFAT Supported?</title>
239
240 <para>
241 <literallayout class='monospaced'>
242I entered runqemu qemux86 and it fires upthis fires up the emulator and uses the
243image and filesystem in the build area created in the previous section.
244
245Then I copied over a pre-created and formated 5.2MB VFAT file named vfat.img.
246I did this with scp vfat.img root@192.168.7.2:
247The file is in the root directory.
248I had to do this because the mkfs.vfat vfat.img command does not work.
249mkfs is not recognized in the qemu terminal session.
250
251when I try mount -o loop -t vfat vfat.img mnt/ I get the error
252mount: can't set up loop device: No space left on device.
253This error is because the loop module is not currently in the kernel image.
254However, this module is available in the
255build area in the tarball modules-2.6.37.6-yocto-starndard+-20-qemux86.tgz.
256You can add this to the kernel image by adding the
257IMAGE_INSTALL += " kernel-module-loop" statement at the top of the local.conf
258file in the build area and then rebuilding the kernel using bitbake.
259It should just build whatever is necessary and not go through an entire build again.
260
261
262
263
264 The <filename>menuconfig</filename> tool provides an interactive method with which
265 to set kernel configurations.
266 In order to use <filename>menuconfig</filename> from within the BitBake environment
267 you need to source an environment setup script.
268 This script is located in the local Yocto Project file structure and is called
269 <filename>oe-init-build-env</filename>.
270 </para>
271
272 <para>
273 The following command sets up the environment:
274 <literallayout class='monospaced'>
275 $ cd ~/poky
276 $ source oe-init-build-env
277 $ runqemu qemux86
278 Continuing with the following parameters:
279 KERNEL: [/home/scottrif/poky/build/tmp/deploy/images/bzImage-qemux86.bin]
280 ROOTFS: [/home/scottrif/poky/build/tmp/deploy/images/core-image-sato-qemux86.ext3]
281 FSTYPE: [ext3]
282 Setting up tap interface under sudo
283 Acquiring lockfile for tap0...
284 WARNING: distccd not present, no distcc support loaded.
285 Running qemu...
286 /home/scottrif/poky/build/tmp/sysroots/x86_64-linux/usr/bin/qemu
287 -kernel /home/scottrif/poky/build/tmp/deploy/images/bzImage-qemux86.bin
288 -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no
289 -hda /home/scottrif/poky/build/tmp/deploy/images/core-image-sato-qemux86.ext3
290 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -enable-gl -no-reboot
291 -m 128 --append "vga=0 root=/dev/hda rw mem=128M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 "
292 Enabling opengl
293 vmsvga_value_write: guest runs Linux.
294 </literallayout>
295 </para>
296 </section>
297
237 <section id='prepare-to-use-menuconfig'> 298 <section id='prepare-to-use-menuconfig'>
238 <title>Prepare to use <filename>menuconfig</filename></title> 299 <title>Prepare to use <filename>menuconfig</filename></title>
239 300