From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc
Date: Sun, 31 Jan 2016 15:54:03 +0000 [thread overview]
Message-ID: <56AE2E1B.6030106@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA_syW-_rM3yuOPzXPUB245=xnBJEPFeJn0ghfJbBdM+7Q@mail.gmail.com>
On 31/01/16 15:34, Peter Maydell wrote:
> On 31 January 2016 at 15:19, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
>> Hi Daniel,
>>
>> Commit d0d7708ba29cbcc343364a46bff981e0ff88366f "qemu-char: add logfile
>> facility to all chardev backends" appears to be causing problems with
>> the monitor and stdin/stdout on both qemu-system-sparc/qemu-system-ppc here.
>
> These should be fixed by https://patchwork.ozlabs.org/patch/571128/
> I think (the duplicate output at least; the multiple-echoback I'm
> not so sure about).
Aha! A quick test here shows that the patch fixes the serial port
appearing on stdout and entering the monitor, but I still see the
multiple echo problem in the GTK GUI.
I also notice that with the above commit I lose cycling through history
in the GTK monitor - even with the multiple echo, instead of the up/down
arrow keys cycling through the history instead I see the codes ^[[B and
^[[A being output to the window instead.
ATB,
Mark.
next prev parent reply other threads:[~2016-01-31 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 15:19 [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc Mark Cave-Ayland
2016-01-31 15:34 ` Peter Maydell
2016-01-31 15:54 ` Mark Cave-Ayland [this message]
2016-01-31 17:19 ` Paolo Bonzini
2016-01-31 17:54 ` Peter Maydell
2016-01-31 21:57 ` Paolo Bonzini
2016-02-02 7:47 ` Mark Cave-Ayland
2016-02-08 9:08 ` Paolo Bonzini
2016-02-08 21:44 ` Mark Cave-Ayland
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=56AE2E1B.6030106@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--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 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.