All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andrew Jones" <drjones@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"QEMU Trivial" <qemu-trivial@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports
Date: Thu, 26 Oct 2017 18:15:57 +0200	[thread overview]
Message-ID: <CAHmME9pE79krWx-zD=VGiScT4c=4TZ1wVxYFiF3m+8wsx9Fqeg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8O6YyS1tSzaydckFpsqpb8HXgW5PJe-VTWud_5YGdW5A@mail.gmail.com>

On Thu, Oct 26, 2017 at 4:36 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> This has *never* been guaranteed or indeed true. It's just happened
> to be true for the x86 PC machine and perhaps for some others that
> you've been using. For instance, the MIPS boston board only has
> one uart. highbank has one. integratorcp has 2. The microblaze
> boards only have one uart. And so on. In cases where we're
> modelling real hardware, if the real board only has one UART
> then we're only going to provide one UART, so in some cases you
> just have to deal with that and have some way in your communication
> protocol to multiplex across a single communications channel.

Interesting. Malta provides quite a few, which is what I'm using on
MIPS, so I guess I've benefited from the uniformity. Since the ARM
virt machine is virtual, it seems like it'd be worthwhile to make it
broadly useful, and adding a few more serial outputs is basically
free.

Right now on build.wireguard.com, I'm just using this horrendous patch
that hopefully hurts to look at: https://א.cc/iKBdlvI3/patch (since I
only need 2). The goal would be for everything else to remain the same
in the deployment, but to not have to use that patch.


>> Could we just do the simple patch of adding four pl011s in there?
>
> I'm still thinking about this. (You definitely can't have four,
> though, because we already have 2 in the trustzone-enabled
> config, so we can only add another 2.)

The trustzone one could be the 5th? Since it's only useful for trustzone.

  reply	other threads:[~2017-10-26 16:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 12:27 [Qemu-devel] [PATCH] hw/arm/virt: support 4 serial ports Jason A. Donenfeld
2017-10-23 12:35 ` no-reply
2017-10-23 13:11 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2017-10-23 13:48   ` Philippe Mathieu-Daudé
2017-10-24 17:57     ` Jason A. Donenfeld
2017-10-26 13:34       ` Andrew Jones
2017-10-26 14:13         ` Jason A. Donenfeld
2017-10-26 14:36           ` Peter Maydell
2017-10-26 16:15             ` Jason A. Donenfeld [this message]
2017-10-26 16:34               ` Peter Maydell
2017-10-26 16:36                 ` Jason A. Donenfeld
2017-10-26 16:41                   ` Peter Maydell
2017-10-26 17:31                     ` Jason A. Donenfeld
2017-12-08 11:49                       ` Peter Maydell
2017-12-08 18:39                         ` Jason A. Donenfeld
2017-12-10 18:15                           ` Peter Maydell
2017-10-23 14:14   ` Jason A. Donenfeld

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='CAHmME9pE79krWx-zD=VGiScT4c=4TZ1wVxYFiF3m+8wsx9Fqeg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=drjones@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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.