qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] more serial ports on arm?
Date: Mon, 10 Dec 2018 12:12:47 +0100	[thread overview]
Message-ID: <f6cc8816-65ea-fe75-2f00-2c741566dda8@redhat.com> (raw)
In-Reply-To: <CAFEAcA-J8gWONJye0JvuwG5warWKZD1MX-GW8=BPuCo9wF5ziQ@mail.gmail.com>

On 12/10/18 12:09 PM, Peter Maydell wrote:
> On Mon, 10 Dec 2018 at 11:00, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> Hi Jason,
>>
>> On 12/7/18 5:42 AM, Jason A. Donenfeld wrote:
>>> On Tue, Nov 20, 2018 at 11:08 AM Peter Maydell <peter.maydell@linaro.org> wrote:
>>>> It's still stuck, because unconditionally adding a second serial
>>>> port to the virt board breaks some commonly used existing guest
>>>> code (UEFI + Linux), and it's not clear to me what the best
>>>> command line UI is for allowing the user to request the second
>>>> serial port.
>>>
>>> Can the UI be the same more or less as for x86? Specify a second
>>> -serial, and then the machine gets one added? If it's in secure mode,
>>> then it's added as serial 3 instead of 2, to remain backwards
>>> compatible.
>>
>> You can use various -serial arguments.
>>
>> If a board supports 4 serials and you only want to see the 3rd (secure
>> mode as your example) you could use:
>>
>> ./qemu -serial null -serial null -serial stdio
> 
> That's the opposite of Jason's issue, which is that the 'virt'
> board only supports 1 serial port but he would like 2...

Oh sorry Jason, I misunderstood your question.

Regards,

Phil.

      reply	other threads:[~2018-12-10 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 23:46 [Qemu-devel] more serial ports on arm? Jason A. Donenfeld
2018-11-20 10:08 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2018-12-07  4:42   ` Jason A. Donenfeld
2018-12-07 10:41     ` Peter Maydell
2018-12-10 11:00     ` Philippe Mathieu-Daudé
2018-12-10 11:09       ` Peter Maydell
2018-12-10 11:12         ` Philippe Mathieu-Daudé [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=f6cc8816-65ea-fe75-2f00-2c741566dda8@redhat.com \
    --to=philmd@redhat.com \
    --cc=Jason@zx2c4.com \
    --cc=peter.maydell@linaro.org \
    --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).