sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Updated 2.2 migration for runqemu porting to python 

Indicated that the configuration file is not mandatory.  Also,
documented the supported qemu* machines should you run the
script without a configuration file.

(From yocto-docs rev: aeb2c28d7476f67302a1b51da51fb57027e9d02c)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-10-19 07:54:57 -07:00 committed by Richard Purdie
parent 952a47b42c
commit 3769f7ba06
1 changed files with 40 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
documentation/ref-manual/migration.xml
View File

@ -3493,16 +3493,21 @@
<para>
The new <filename>runqemu</filename> is a Python script.
The script requires a configuration file in the following
form in order to boot the BSP:
Machine knowledge is no longer hardcoded into
<filename>runqemu</filename>.
You can choose to use the <filename>qemuboot</filename>
configuration file to define the BSP's own arguments and to make
it bootable with <filename>runqemu</filename>.
If you use a configuration file, use the following form:
<literallayout class='monospaced'>
<replaceable>image-name</replaceable>-<replaceable>machine</replaceable>.qemuboot.conf
</literallayout>
Machine knowledge is no longer hardcoded into
<filename>runqemu</filename>.
You can use the <filename>qemuboot</filename> configuration file
to define the BSP's own arguments and to make it bootable
with <filename>runqemu</filename>.
The configuration file enables fine-grained tuning of options
passed to QEMU without the <filename>runqemu</filename> script
hard-coding any knowledge about different machines.
Using a configuration file is particularly convenient when trying
to use QEMU with machines other than the
<filename>qemu*</filename> machines in OE-Core.
<note>
Previous usage patterns are continued to be supported.
</note>
@ -3515,6 +3520,34 @@
<filename>qemuboot.conf</filename>.
</para>
<para>
If you want to use <filename>runqemu</filename> without a
configuration file, use the following command form:
<literallayout class='monospaced'>
$ runqemu <replaceable>machine</replaceable> <replaceable>rootfs</replaceable> <replaceable>kernel</replaceable> [<replaceable>options</replaceable>]
</literallayout>
Supported <replaceable>machines</replaceable> are as follows:
<literallayout class='monospaced'>
qemuarm
qemuarm64
qemux86
qemux86-64
qemuppc
qemumips
qemumips64
qemumipsel
qemumips64el
</literallayout>
Consider the following example, which uses the
<filename>qemux86-64</filename> machine,
provides a root filesystem, provides an image, and uses
the <filename>nographic</filename> option:
<literallayout class='monospaced'>
$ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4 tmp/deploy/images/qemux86-64/bzImage nographic
</literallayout>
</para>
<para>
Following is a list of variables that can be set in configuration
files such as <filename>bsp.conf</filename> to enable the BSP