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: Fri, 8 Dec 2017 19:39:14 +0100	[thread overview]
Message-ID: <CAHmME9rSEtwg=n1gtqOVh=Et5yn45Yveh3LEFj357aqRZXwwcQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-5F2GMx9UNoH=LJAa-m1DXg2HW8PJZ47kurjx5x3NhWA@mail.gmail.com>

On Fri, Dec 8, 2017 at 12:49 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> Now that the 2.11 release is mostly out of the way, I've been
> working through some of my other todo list items so I've
> come back to this thread.
>
> My suggestion is that we should add a second non-secure UART
> to the virt board, so if you're using secure=no then you
> get serial 1 and 2, and for secure=yes serial 1 is the first
> NS uart, serial 2 is the secure uart and serial 3 is the
> 2nd NS uart. (I don't really want to add a 4th uart unless
> there's some good reason to -- maybe we would turn out to
> want it for the secure side, for instance.)
>
> I'll probably write a patch for this next week, unless you
> want to do it.

Sounds great to me. Thanks!

I'm curious why you don't want to add a 4th UART. It seems trivial to
do, and the more the merrier? Or that's a silly attitude? Mostly just
curious about that, as having two personally suits my needs.

  reply	other threads:[~2017-12-08 18:39 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
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 [this message]
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='CAHmME9rSEtwg=n1gtqOVh=Et5yn45Yveh3LEFj357aqRZXwwcQ@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.