From: Laszlo Ersek <lersek@redhat.com>
To: "Gabriel L. Somlo" <somlo@cmu.edu>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, gsomlo@gmail.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] fw_cfg: document MMIO registers for arm, sun4*, and ppc/mac_*
Date: Thu, 6 Aug 2015 11:14:25 +0200 [thread overview]
Message-ID: <55C32571.5000103@redhat.com> (raw)
In-Reply-To: <1438818474-31373-3-git-send-email-somlo@cmu.edu>
On 08/06/15 01:47, Gabriel L. Somlo wrote:
> Signed-off-by: Gabriel Somlo <somlo@cmu.edu>
> ---
> docs/specs/fw_cfg.txt | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/docs/specs/fw_cfg.txt b/docs/specs/fw_cfg.txt
> index 5bc7b96..f37e1ad 100644
> --- a/docs/specs/fw_cfg.txt
> +++ b/docs/specs/fw_cfg.txt
> @@ -72,10 +72,26 @@ increasing address order, similar to memcpy().
>
> == Register Locations ==
>
> -=== x86, x86_64 Register Locations ===
> +=== x86, x86_64, sun4u Register Locations ===
> +
> +Selector Register IOport: 0x510 (16-bit, little-endian)
> +Data Register IOport: 0x511 (8-bit)
> +
> +=== arm Register Locations ===
> +
> +Selector Register MMIO addr: 0x9020008 (16-bit, big-endian)
> +Data Register MMIO addr: 0x9020000 (64-bit)
Suggestions:
- maybe mention that this is specific to the "virt" machtype
- mention that the exact location comes from the DTB,
and hint at "Documentation/devicetree/bindings/arm/fw-cfg.txt" in the
kernel tree
- for the data register, rather than just "(64-bit)", consider saying
"(64-bit, endianless, string-preserving)"
> +
> +=== sun4m Register Locations ===
> +
> +Selector Register MMIO addr: 0xd00000510 (16-bit, big-endian)
> +Data Register MMIO addr: 0xd00000512 (8-bit)
> +
> +=== ppc/mac Register Locations ===
> +
> +Selector Register MMIO addr: 0xf0000510 (16-bit, big-endian)
> +Data Register MMIO addr: 0xf0000512 (8-bit)
Should these be tied to machine types? (I got no clue, I've never even
built these targets.)
Thanks
Laszlo
>
> -Selector Register IOport: 0x510
> -Data Register IOport: 0x511
>
> == Firmware Configuration Items ==
>
>
next prev parent reply other threads:[~2015-08-06 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 23:47 [Qemu-devel] [PATCH v2 0/2] fw_cfg: documentation updates for v2.4 Gabriel L. Somlo
2015-08-05 23:47 ` [Qemu-devel] [PATCH v2 1/2] fw_cfg: document fw_cfg_modify_iXX() update functions Gabriel L. Somlo
2015-08-06 9:01 ` Laszlo Ersek
2015-08-05 23:47 ` [Qemu-devel] [PATCH v2 2/2] fw_cfg: document MMIO registers for arm, sun4*, and ppc/mac_* Gabriel L. Somlo
2015-08-06 9:14 ` Laszlo Ersek [this message]
2015-08-06 13:15 ` Peter Maydell
2015-08-06 14:49 ` Gabriel L. Somlo
2015-08-06 14:53 ` Peter Maydell
2015-08-06 7:58 ` [Qemu-devel] [PATCH v2 0/2] fw_cfg: documentation updates for v2.4 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=55C32571.5000103@redhat.com \
--to=lersek@redhat.com \
--cc=gsomlo@gmail.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.