summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml15
1 files changed, 13 insertions, 2 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index f62eac16d7..24480bc787 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -471,8 +471,19 @@
471 $ source /opt/poky/environment-setup-i586-poky-linux 471 $ source /opt/poky/environment-setup-i586-poky-linux
472 $ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3 472 $ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3
473 </literallayout> 473 </literallayout>
474 </section> 474
475 475 <para>
476 The environment in which QEMU launches varies depending on the filesystem image and on the
477 target architecture. For example, if you source the environment for the ARM target
478 architecture and then boot the minimal QEMU image, the emulator comes up in a new
479 shell in command-line mode. However, if you boot the SDK image QEMU comes up with
480 a GUI.
481 </para>
482
483 <note><para>
484 Booting the PPC image results in QEMU launching in the same shell in command-line mode.
485 </para></note>
486 </section>
476 </section> 487 </section>
477</section> 488</section>
478 489