From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] 2nd serial port by default
Date: Fri, 12 Dec 2008 23:10:03 +0000 [thread overview]
Message-ID: <20081212231003.GA9384@miranda.arrow> (raw)
In-Reply-To: <200812081226.40842.paul@codesourcery.com>
On Mon, Dec 08, 2008 at 12:26:40PM +0000, Paul Brook wrote:
> In practice I'd expect that by far the most common use for serial ports is a
> serial console, and one is more than sufficient for that. If you want to do
> anything else then you're probably going to need special -serial options
> anyway.
The issue here is that the MIPS Magnum has two serial ports, and its
firmware checks that both serial ports are functioning and complains
if either of them is not. If the user only needs a single serial port,
then they currently have to pass '-serial null' for the second port.
IMO, the default number of ports that are emulated should depend on the
machine that is being emulated.
Cheers,
--
Stuart Brady
prev parent reply other threads:[~2008-12-12 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 21:05 [Qemu-devel] [RFC] 2nd serial port by default Hervé Poussineau
2008-12-08 12:26 ` Paul Brook
2008-12-12 23:10 ` Stuart Brady [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=20081212231003.GA9384@miranda.arrow \
--to=sdbrady@ntlworld.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).