[gnome-continuous-yocto/gnomeostree-3.28-rocko: 3060/8267] ref-manual: Updated 2.2 migration for runqemu porting to python
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-continuous-yocto/gnomeostree-3.28-rocko: 3060/8267] ref-manual: Updated 2.2 migration for runqemu porting to python
- Date: Sun, 17 Dec 2017 00:06:12 +0000 (UTC)
commit 3769f7ba06dcf48ecba250483d895256b4c52d16
Author: Scott Rifenbark <srifenbark gmail com>
Date: Wed Oct 19 07:54:57 2016 -0700
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>
documentation/ref-manual/migration.xml | 47 +++++++++++++++++++++++++++-----
1 files changed, 40 insertions(+), 7 deletions(-)
---
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index bd70ca7..64f6da8 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]