From 74c24e08af245404f0c9aac9b9313170b4b03c7f Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 20 Jan 2011 15:07:21 -0800 Subject: documentation/yocto-project-qs/yocto-project-qs.xml: Added note to poky-qemu command Depending on the architecture you are booting and the profile of the filesystem image QEMU might come up in a new shell, and existing shell, have a GUI, or be in command-line mode. I added a note indicating this behavior. Signed-off-by: Scott Rifenbark --- documentation/yocto-project-qs/yocto-project-qs.xml | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'documentation/yocto-project-qs') diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index f62eac1..24480bc 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -471,8 +471,19 @@ $ source /opt/poky/environment-setup-i586-poky-linux $ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3 - - + + + The environment in which QEMU launches varies depending on the filesystem image and on the + target architecture. For example, if you source the environment for the ARM target + architecture and then boot the minimal QEMU image, the emulator comes up in a new + shell in command-line mode. However, if you boot the SDK image QEMU comes up with + a GUI. + + + + Booting the PPC image results in QEMU launching in the same shell in command-line mode. + + -- cgit v1.1