qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode
Date: Tue, 3 Jul 2018 21:08:13 +0100	[thread overview]
Message-ID: <CAFEAcA9pa7YTLnHYD0c7GvkkmiwD+Yyk9qr6G_EC2JeWdMB26Q@mail.gmail.com> (raw)
In-Reply-To: <20180703184922.GA14422@roeck-us.net>

On 3 July 2018 at 19:49, Guenter Roeck <linux@roeck-us.net> wrote:
> Oddly enough, I now seem to be unable to reproduce the problem either.
> Weird, when I wrote the patch it was absolutely necessary.
>
> The only other change I can think of would be the code to set the
> serial baud rate in the boot loader, which I did not have initially.
> Is it possible that the hangup could have been caused by that ?

Seems unlikely -- unless you're actually connecting the emulated
serial port to a real host serial port, we don't do anything with
the baudrate in the cmsdk uart model except complain if the
guest hasn't set it to something valid.

> Is it worth tracking it down, or are we ok ?

It does worry me a little, but if neither you nor I can repro
it at the moment there's not a lot we can do about it I think.
Looking at the ptimer and cmsdk timer code I think it *should*
now implement what the hardware does...

If you see the problem again in future let me know and we
can have another go at figuring out what's going on.

> The series WFM as well. I'll send out a Tested-by: in a minute.

Thanks for the testing.

-- PMM

      reply	other threads:[~2018-07-03 20:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  2:08 [Qemu-devel] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode Guenter Roeck
2018-06-26 17:17 ` Peter Maydell
2018-06-26 17:59   ` Guenter Roeck
2018-06-26 18:10     ` Peter Maydell
2018-06-26 18:43       ` Guenter Roeck
2018-06-26 20:00       ` Guenter Roeck
2018-07-02 15:05         ` Peter Maydell
2018-07-02 15:29           ` Peter Maydell
2018-07-02 16:27           ` Guenter Roeck
2018-07-02 16:46             ` Peter Maydell
2018-07-02 17:05               ` Guenter Roeck
2018-07-02 17:10                 ` Peter Maydell
2018-07-02 17:57                   ` Guenter Roeck
2018-07-02 18:06                     ` Peter Maydell
2018-07-02 18:37                       ` Guenter Roeck
2018-07-03 17:06                         ` Peter Maydell
2018-07-03 18:49                           ` Guenter Roeck
2018-07-03 20:08                             ` Peter Maydell [this message]

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=CAFEAcA9pa7YTLnHYD0c7GvkkmiwD+Yyk9qr6G_EC2JeWdMB26Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=linux@roeck-us.net \
    --cc=qemu-arm@nongnu.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).