diff options
author | Ulrich Ölmann <u.oelmann@pengutronix.de> | 2022-08-31 13:21:26 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-08-31 12:25:44 +0100 |
commit | 4c2f9073d6a8fb8bca198ff1f602c37c5afa691e (patch) | |
tree | 529d611fa0a1ada0e142c5cec38068b5f8b41a2a /scripts/runqemu.README | |
parent | f6bd4af0d9d61dfbab6a34bd349bad65b405ae7d (diff) | |
download | poky-4c2f9073d6a8fb8bca198ff1f602c37c5afa691e.tar.gz |
scripts/runqemu.README: fix typos and trailing whitespaces
(From OE-Core rev: 217b00d378f359689613ca4c0666bb2eed040f69)
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/runqemu.README')
-rw-r--r-- | scripts/runqemu.README | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/scripts/runqemu.README b/scripts/runqemu.README index da9abd7dfb..e5f4b4634c 100644 --- a/scripts/runqemu.README +++ b/scripts/runqemu.README | |||
@@ -1,12 +1,12 @@ | |||
1 | Using OE images with QEMU | 1 | Using OE images with QEMU |
2 | ========================= | 2 | ========================= |
3 | 3 | ||
4 | OE-Core can generate qemu bootable kernels and images with can be used | 4 | OE-Core can generate qemu bootable kernels and images which can be used |
5 | on a desktop system. The scripts currently support booting ARM, MIPS, PowerPC | 5 | on a desktop system. The scripts currently support booting ARM, MIPS, PowerPC |
6 | and x86 (32 and 64 bit) images. The scripts can be used within the OE build | 6 | and x86 (32 and 64 bit) images. The scripts can be used within the OE build |
7 | system or externaly. | 7 | system or externally. |
8 | 8 | ||
9 | The runqemu script is run as: | 9 | The runqemu script is run as: |
10 | 10 | ||
11 | runqemu <machine> <zimage> <filesystem> | 11 | runqemu <machine> <zimage> <filesystem> |
12 | 12 | ||
@@ -15,13 +15,13 @@ where: | |||
15 | <machine> is the machine/architecture to use (qemuarm/qemumips/qemuppc/qemux86/qemux86-64) | 15 | <machine> is the machine/architecture to use (qemuarm/qemumips/qemuppc/qemux86/qemux86-64) |
16 | <zimage> is the path to a kernel (e.g. zimage-qemuarm.bin) | 16 | <zimage> is the path to a kernel (e.g. zimage-qemuarm.bin) |
17 | <filesystem> is the path to an ext2 image (e.g. filesystem-qemuarm.ext2) or an nfs directory | 17 | <filesystem> is the path to an ext2 image (e.g. filesystem-qemuarm.ext2) or an nfs directory |
18 | 18 | ||
19 | If <machine> isn't specified, the script will try to detect the machine name | 19 | If <machine> isn't specified, the script will try to detect the machine name |
20 | from the name of the <zimage> file. | 20 | from the name of the <zimage> file. |
21 | 21 | ||
22 | If <filesystem> isn't specified, nfs booting will be assumed. | 22 | If <filesystem> isn't specified, nfs booting will be assumed. |
23 | 23 | ||
24 | When used within the build system, it will default to qemuarm, ext2 and the last kernel and | 24 | When used within the build system, it will default to qemuarm, ext2 and the last kernel and |
25 | core-image-sato-sdk image built by the build system. If an sdk image isn't present it will look | 25 | core-image-sato-sdk image built by the build system. If an sdk image isn't present it will look |
26 | for sato and minimal images. | 26 | for sato and minimal images. |
27 | 27 | ||
@@ -31,7 +31,7 @@ Full usage instructions can be seen by running the command with no options speci | |||
31 | Notes | 31 | Notes |
32 | ===== | 32 | ===== |
33 | 33 | ||
34 | - The scripts run qemu using sudo. Change perms on /dev/net/tun to | 34 | - The scripts run qemu using sudo. Change perms on /dev/net/tun to |
35 | run as non root. The runqemu-gen-tapdevs script can also be used by | 35 | run as non root. The runqemu-gen-tapdevs script can also be used by |
36 | root to prepopulate the appropriate network devices. | 36 | root to prepopulate the appropriate network devices. |
37 | - You can access the host computer at 192.168.7.1 within the image. | 37 | - You can access the host computer at 192.168.7.1 within the image. |