From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 07/10] PPC: guts: Add emulation of a few more registers
Date: Wed, 22 Jan 2014 18:08:38 -0600 [thread overview]
Message-ID: <1390435718.24905.525.camel@snotra.buserror.net> (raw)
In-Reply-To: <1390175077-5717-8-git-send-email-agraf@suse.de>
On Mon, 2014-01-20 at 00:44 +0100, Alexander Graf wrote:
> The GUTS device is used by system software to find out about hardware
> details of the current system.
>
> We only emulate the bare minimum to be able to reboot a guest which is
> not sufficient to make u-boot happy.
>
> Add a few more registers to our portfolio with dummy values.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> hw/ppc/mpc8544_guts.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/hw/ppc/mpc8544_guts.c b/hw/ppc/mpc8544_guts.c
> index a10abe9..af8c742 100644
> --- a/hw/ppc/mpc8544_guts.c
> +++ b/hw/ppc/mpc8544_guts.c
> @@ -25,6 +25,8 @@
> #define MPC8544_GUTS_RSTCR_RESET 0x02
>
> #define MPC8544_GUTS_ADDR_PORPLLSR 0x00
> +#define PORPLLSR_SYS_RATIO_MAX 0x3e
> +#define PORPLLSR_CPU0_RATIO_MAX (0x3f << 16)
> #define MPC8544_GUTS_ADDR_PORBMSR 0x04
> #define MPC8544_GUTS_ADDR_PORIMPSCR 0x08
> #define MPC8544_GUTS_ADDR_PORDEVSR 0x0C
> @@ -36,6 +38,7 @@
> #define MPC8544_GUTS_ADDR_GPINDR 0x50
> #define MPC8544_GUTS_ADDR_PMUXCR 0x60
> #define MPC8544_GUTS_ADDR_DEVDISR 0x70
> +#define DEVDISR_DISABLED_NONE 0x0
> #define MPC8544_GUTS_ADDR_POWMGTCSR 0x80
> #define MPC8544_GUTS_ADDR_MCPSUMR 0x90
> #define MPC8544_GUTS_ADDR_RSTRSCR 0x94
> @@ -73,6 +76,15 @@ static uint64_t mpc8544_guts_read(void *opaque, hwaddr addr,
>
> addr &= MPC8544_GUTS_MMIO_SIZE - 1;
> switch (addr) {
> + case MPC8544_GUTS_ADDR_PORPLLSR:
> + value = PORPLLSR_SYS_RATIO_MAX | PORPLLSR_CPU0_RATIO_MAX;
> + break;
> + case MPC8544_GUTS_ADDR_PORDEVSR:
> + value = 0;
> + break;
> + case MPC8544_GUTS_ADDR_DEVDISR:
> + value = DEVDISR_DISABLED_NONE;
> + break;
But we don't actually have most of these devices that you're claiming
aren't disabled via DEVDISR -- and with the paravirt target, what do
these registers even mean?
I'd rather see U-Boot not touch these registers for the QEMU target,
rather than returning arbitrary values.
-Scott
next prev parent reply other threads:[~2014-01-23 0:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 23:44 [Qemu-devel] [PATCH 00/10] PPC: e500: Use u-boot as firmware Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 01/10] PPC: Make all e500 CPUs SVR aware Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 02/10] PPC: Add definitions for GIVORs Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 03/10] PPC: Add stub emulation for HDBCR0 Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 04/10] PPC: Add L1CFG1 SPR emulation Alexander Graf
2014-01-23 0:15 ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2014-01-19 23:44 ` [Qemu-devel] [PATCH 05/10] PPC: Properly emulate L1CSR0 and L1CSR1 Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 06/10] PPC: Add dcbtls emulation Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 07/10] PPC: guts: Add emulation of a few more registers Alexander Graf
2014-01-23 0:08 ` Scott Wood [this message]
2014-01-23 11:34 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-01-23 21:22 ` Scott Wood
2014-01-19 23:44 ` [Qemu-devel] [PATCH 08/10] PPC: e500: Expose kernel load address in dt Alexander Graf
2014-01-19 23:44 ` [Qemu-devel] [PATCH 09/10] PPC: Add u-boot firmware for e500 Alexander Graf
2014-01-20 0:17 ` Peter Maydell
2014-01-20 10:04 ` Alexander Graf
2014-01-23 0:13 ` Scott Wood
2014-01-19 23:44 ` [Qemu-devel] [PATCH 10/10] PPC: e500: Move to u-boot as firmware Alexander Graf
2014-01-23 0:23 ` Scott Wood
2014-01-23 10:40 ` Alexander Graf
2014-01-23 22:22 ` Scott Wood
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=1390435718.24905.525.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).