qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bohdan Kostiv <bogdan.kostiv@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] Fixed '-serial none' usage breaks following '-serial ...' usage
Date: Fri, 12 Jan 2024 18:30:44 +0000	[thread overview]
Message-ID: <CAFEAcA8mJU16UL_H4wXGNh77nkuoMc3XMwtnAaV5XwdFn2f=sQ@mail.gmail.com> (raw)
In-Reply-To: <CAA3Sv1LQ8yDUNLCB5WqLVZjsHffrU0uSbL_YYJW_m+Db2PhEeQ@mail.gmail.com>

On Wed, 10 Jan 2024 at 14:38, Bohdan Kostiv <bogdan.kostiv@gmail.com> wrote:
>
> Hello,
>
> I have faced an issue in using serial ports when I need to skip a couple of ports in the CLI.
>
> For example the ARM machine netduinoplus2 supports up to 7 UARTS.
> Following case works (the first UART is used to send data in the firmware):
> qemu-system-arm -machine netduinoplus2 -nographic -serial mon:stdio -kernel path-to-fw/firmware.elf
> But this one doesn't  (the third UART is used to send data in the firmware):
> qemu-system-arm -machine netduinoplus2 -nographic -serial none -serial none -serial mon:stdio -kernel path-to-fw/firmware.elf

Thanks for this patch. I'll have a think about whether it's
the right fix next week. In the meantime, I suspect you'll find
that if you use "-serial null -serial null -serial mon:stdio" in
your command line example you'll find that does what you're aiming for.

("-serial none" means "don't create a serial port device", whereas
"-serial null" means "create a serial port device, but have its
input and output go to nowhere".)

thanks
-- PMM


  reply	other threads:[~2024-01-12 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  7:46 [PATCH] Fixed '-serial none' usage breaks following '-serial ...' usage Bohdan Kostiv
2024-01-12 18:30 ` Peter Maydell [this message]
2024-01-15 16:14 ` Peter Maydell
2024-01-16  7:33   ` Markus Armbruster
2024-01-16 17:34   ` Daniel P. Berrangé
2024-01-22 15:54   ` 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='CAFEAcA8mJU16UL_H4wXGNh77nkuoMc3XMwtnAaV5XwdFn2f=sQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=bogdan.kostiv@gmail.com \
    --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).