From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: alistair@alistair23.me, Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH] docs/generic-loader: mention U-Boot and Intel HEX executable formats
Date: Thu, 16 Aug 2018 15:55:54 +0100 [thread overview]
Message-ID: <20180816145554.9814-1-stefanha@redhat.com> (raw)
The generic loader device supports the U-Boot and Intel HEX executable
formats in addition to the document raw and ELF formats. Reword the
documentation to include these formats and explain how various options
depend on the executable format.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
Based-on: <20180816133438.17061-1-peter.maydell@linaro.org>
(https://git.linaro.org/people/pmaydell/qemu-arm.git/ pull-target-arm-20180816)
docs/generic-loader.txt | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/generic-loader.txt b/docs/generic-loader.txt
index 31bbcd42f6..a9603a2af7 100644
--- a/docs/generic-loader.txt
+++ b/docs/generic-loader.txt
@@ -56,25 +56,25 @@ An example of setting CPU 0's PC to 0x8000 is:
Loading Files
-------------
-The loader device also allows files to be loaded into memory. It can load raw
-files and ELF executable files. Raw files are loaded verbatim. ELF executable
-files are loaded by an ELF loader. The syntax is shown below:
+The loader device also allows files to be loaded into memory. It can load ELF,
+U-Boot, and Intel HEX executable formats as well as raw images. The syntax is
+shown below:
-device loader,file=<file>[,addr=<addr>][,cpu-num=<cpu-num>][,force-raw=<raw>]
<file> - A file to be loaded into memory
- <addr> - The addr in memory that the file should be loaded. This is
- ignored if you are using an ELF (unless force-raw is true).
- This is required if you aren't loading an ELF.
+ <addr> - The memory address where the file should be loaded. This is
+ required for raw images and ignored for non-raw files.
<cpu-num> - This specifies the CPU that should be used. This is an
optional argument and will cause the CPU's PC to be set to
- where the image is stored or in the case of an ELF file to
- the value in the header. This option should only be used
- for the boot image.
+ the memory address where the raw file is loaded or the entry
+ point specified in the executable format header. This option
+ should only be used for the boot image.
This will also cause the image to be written to the specified
CPU's address space. If not specified, the default is CPU 0.
<force-raw> - Setting force-raw=on forces the file to be treated as a raw
- image. This can be used to load ELF files as if they were raw.
+ image. This can be used to load supported executable formats
+ as if they were raw.
All values are parsed using the standard QemuOps parsing. This allows the user
to specify any values in any format supported. By default the values
--
2.17.1
next reply other threads:[~2018-08-16 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 14:55 Stefan Hajnoczi [this message]
2018-08-16 15:54 ` [Qemu-devel] [PATCH] docs/generic-loader: mention U-Boot and Intel HEX executable formats Alistair Francis
2018-08-16 16:42 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180816145554.9814-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=alistair@alistair23.me \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).