From: Peter Maydell <peter.maydell@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Drew Jones <drjones@redhat.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Andrea Bolognani <abologna@redhat.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH 3/3] hw/arm/virt-acpi-build: Add second UART to ACPI tables
Date: Tue, 12 Dec 2017 14:17:49 +0000 [thread overview]
Message-ID: <CAFEAcA8OY3PFk_bermKxQBuF_th7SudHgaRk8wf76EAGYnoCGw@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu8gZ-Y4-zV2GRgbXPcignAg3vi8__XaFXqAhYOZOL7GcQ@mail.gmail.com>
On 12 December 2017 at 14:16, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 12 December 2017 at 14:13, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 12 December 2017 at 14:12, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>>> On 12 December 2017 at 14:10, Peter Maydell <peter.maydell@linaro.org> wrote:
>>>> That doesn't actually usefully separate debug output from the
>>>> console, though, because stdout-path is also going to point
>>>> to the UART with the lowest physical address...
>>>>
>>>
>>> By default, yes, just like is currently the case. But I would assume
>>> this new serial port could be appointed 'console' and put into
>>> stdout-path by QEMU, based on the command line options?
>>
>> We don't have any command line options for doing that, and I'm
>> generally reluctant to introduce new command line UI, especially
>> new command line UI that's specific to Arm and not also needed
>> for x86.
>>
>
> If stdout-path is always going to point to pl011@0x9000000, why would
> we need to parse it?
If you had always parsed stdout-path, we wouldn't need to worry
about the order in which the UART nodes appear in the dtb...
thanks
-- PMM
next prev parent reply other threads:[~2017-12-12 14:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 15:02 [Qemu-arm] [PATCH 0/3] hw/arm/virt: Add another UART Peter Maydell
2017-12-08 15:02 ` [Qemu-arm] [PATCH 1/3] hw/arm/virt: Add virt-2.12 machine type Peter Maydell
2017-12-12 14:39 ` [Qemu-arm] [Qemu-devel] " Andrew Jones
2018-01-15 12:00 ` Peter Maydell
2017-12-08 15:02 ` [Qemu-arm] [PATCH 2/3] hw/arm/virt: Add another UART to the virt board Peter Maydell
2017-12-12 5:55 ` [Qemu-arm] [Qemu-devel] " Shannon Zhao
2017-12-12 10:45 ` Peter Maydell
2017-12-12 14:25 ` Jason A. Donenfeld
2017-12-12 14:45 ` [Qemu-arm] " Andrew Jones
2017-12-12 14:50 ` Peter Maydell
2017-12-12 15:16 ` Andrew Jones
2017-12-12 15:51 ` [Qemu-arm] " Peter Maydell
2018-05-31 2:12 ` Jason A. Donenfeld
2018-05-31 8:32 ` [Qemu-arm] " Peter Maydell
2018-05-31 11:48 ` Jason A. Donenfeld
2018-05-31 11:57 ` Peter Maydell
2017-12-12 15:16 ` Andrew Jones
2017-12-08 15:02 ` [Qemu-arm] [PATCH 3/3] hw/arm/virt-acpi-build: Add second UART to ACPI tables Peter Maydell
2017-12-12 5:53 ` [Qemu-devel] " Shannon Zhao
2017-12-12 11:06 ` [Qemu-arm] " Laszlo Ersek
2017-12-12 11:11 ` Peter Maydell
2017-12-12 11:33 ` Laszlo Ersek
2017-12-12 11:44 ` Ard Biesheuvel
2017-12-12 11:59 ` Laszlo Ersek
2017-12-12 12:07 ` Peter Maydell
2017-12-12 12:41 ` Laszlo Ersek
2017-12-12 12:47 ` Peter Maydell
2017-12-12 13:28 ` Laszlo Ersek
2017-12-12 13:56 ` Ard Biesheuvel
2017-12-12 14:10 ` [Qemu-arm] " Peter Maydell
2017-12-12 14:12 ` Ard Biesheuvel
2017-12-12 14:13 ` Peter Maydell
2017-12-12 14:16 ` [Qemu-arm] " Ard Biesheuvel
2017-12-12 14:17 ` Peter Maydell [this message]
2017-12-12 14:31 ` Ard Biesheuvel
2017-12-12 14:51 ` Andrew Jones
2017-12-12 16:38 ` [Qemu-arm] " Laszlo Ersek
2017-12-12 14:18 ` Andrew Jones
2017-12-12 14:10 ` [Qemu-arm] " Andrew Jones
2017-12-12 15:09 ` Andrew Jones
2017-12-13 13:56 ` Peter Maydell
2017-12-13 16:01 ` Laszlo Ersek
2017-12-13 16:46 ` Ard Biesheuvel
2017-12-13 16:48 ` Peter Maydell
2017-12-08 15:10 ` [Qemu-arm] [PATCH 0/3] hw/arm/virt: Add another UART Peter Maydell
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=CAFEAcA8OY3PFk_bermKxQBuF_th7SudHgaRk8wf76EAGYnoCGw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Jason@zx2c4.com \
--cc=abologna@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=drjones@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhaoshenglong@huawei.com \
/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).