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 <scott.m.rifenbark@intel.com>
This commit is contained in:
parent
63e6319bd1
commit
74c24e08af
|
@ -471,8 +471,19 @@
|
||||||
$ source /opt/poky/environment-setup-i586-poky-linux
|
$ 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
|
$ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</section>
|
|
||||||
|
|
||||||
|
<para>
|
||||||
|
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.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<note><para>
|
||||||
|
Booting the PPC image results in QEMU launching in the same shell in command-line mode.
|
||||||
|
</para></note>
|
||||||
|
</section>
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue