From: Guenter Roeck <linux@roeck-us.net>
To: monstr@monstr.eu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Microblaze image hanging in qemu with 3.15-rc
Date: Fri, 25 Apr 2014 06:29:03 -0700 [thread overview]
Message-ID: <535A631F.5020208@roeck-us.net> (raw)
In-Reply-To: <535A0DD7.4080204@monstr.eu>
On 04/25/2014 12:25 AM, Michal Simek wrote:
[ ... ]
>
> It should be pretty easy to fix it in timer_write function like this.
>
> diff --git a/hw/timer/xilinx_timer.c b/hw/timer/xilinx_timer.c
> index 6113b97..3ff1da9 100644
> --- a/hw/timer/xilinx_timer.c
> +++ b/hw/timer/xilinx_timer.c
> @@ -169,7 +169,7 @@ timer_write(void *opaque, hwaddr addr,
> if (value & TCSR_TINT)
> value &= ~TCSR_TINT;
>
> - xt->regs[addr] = value;
> + xt->regs[addr] = value & 0x7ff;
> if (value & TCSR_ENT)
> timer_enable(xt);
> break;
>
Hi Michal,
that fixes endianness detection, but the image is still hanging.
Here is the log:
NR_IRQS:33
/plb@0/interrupt-controller@81800000: num_irq=4, edge=0xa
ERROR: CPU CCF input clock not found
Reading TCSR0 returned 0x0, expected 0x1
Switch to big endian mode
/plb@0/timer@83c00000: irq=1
ERROR: timer CCF input clock not found
ERROR: Using CPU clock frequency
xilinx_timer_set_mode: shutdown
xilinx_timer_set_mode: periodic
sched_clock: 32 bits at 62MHz, resolution 16ns, wraps every 68719476720ns
Calibrating delay loop... QEMU: Terminated
I added a couple of log messages to make sure that the mode is detected correctly.
Any idea what else might be wrong ?
Thanks,
Guenter
next prev parent reply other threads:[~2014-04-25 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 17:23 Microblaze image hanging in qemu with 3.15-rc Guenter Roeck
2014-04-23 5:32 ` Michal Simek
2014-04-23 13:38 ` Guenter Roeck
2014-04-23 14:12 ` Michal Simek
2014-04-23 15:45 ` Guenter Roeck
2014-04-24 6:16 ` Michal Simek
2014-04-24 13:38 ` Guenter Roeck
2014-04-25 7:25 ` Michal Simek
2014-04-25 13:29 ` Guenter Roeck [this message]
2014-04-25 13:51 ` Guenter Roeck
2014-04-25 14:03 ` Michal Simek
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=535A631F.5020208@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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).