From: xiaoqiang zhao <zxq_yx_007@163.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Jérôme Forissier" <jerome.forissier@linaro.org>
Cc: qemu-discuss <qemu-discuss@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-discuss] -serial option broken in master?
Date: Wed, 8 Jun 2016 10:07:27 +0800 [thread overview]
Message-ID: <57577DDF.9070202@163.com> (raw)
In-Reply-To: <CAFEAcA_f+8P6za0rmBNJfXzZjWKHP9W0MHzicgLcDy8KYzQVYw@mail.gmail.com>
在 2016年06月08日 05:24, Peter Maydell 写道:
> On 7 June 2016 at 15:47, Jérôme Forissier <jerome.forissier@linaro.org> wrote:
>> Hi,
>>
>> I just noticed this error [1] (QEMU master branch):
>>
>> ../qemu/arm-softmmu/qemu-system-arm -nographic -monitor none -machine
>> virt -machine secure=on -cpu cortex-a15 -m 1057 -serial stdio -serial
>> file:serial1.log -bios
>> /home/travis/optee_repo/build/../out/bios-qemu/bios.bin
>> Unexpected error in parse_chr() at hw/core/qdev-properties-system.c:149:
>> qemu-system-arm: Property 'pl011.chardev' can't take value 'serial0',
>> it's in use
>>
>> FYI, revert commits e5fabad7ccfd ("char: get rid of
>> qemu_char_get_next_serial") and f0d1d2c115df ("hw/char: QOM'ify pl011
>> model"), and the problem disappears.
>>
>> Should I use a different syntax?
> No, it's a bug that we broke this somehow. Xiaoqiang, could you
> have a look at this, please?
>
> thanks
> -- PMM
Hi, peter:
The bug was caught. It is because in vrit.c, create_uart is called
twice, in which serial_hds array is hardcoded.
I will send a patch to fix this later .
prev parent reply other threads:[~2016-06-08 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5756DE9D.7050603@linaro.org>
2016-06-07 21:24 ` [Qemu-devel] [Qemu-discuss] -serial option broken in master? Peter Maydell
2016-06-07 22:44 ` xiaoqiang zhao
2016-06-08 2:07 ` xiaoqiang zhao [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=57577DDF.9070202@163.com \
--to=zxq_yx_007@163.com \
--cc=jerome.forissier@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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.