From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Serial port passthrough for arm kvm
Date: Tue, 12 May 2015 14:43:41 -0400 [thread overview]
Message-ID: <20150512184341.GO24389@csclub.uwaterloo.ca> (raw)
We are trying to pass a serial port through to an arm guest on kvm and
the serial port is working for passing data, but is not setting the baud
rate when the guest changes it.
If I change the baud rate of the port from the host, then the baud rate
is set correctly and data is passed through just fine.
The emulated system is vexpress a15 with the port passed through with:
-serial /dev/ttyS6
Is there something missing for handling the baud rate from ttyAMA ports
in the guest and updating the setting on the host port?
I am using qemu 2.1 at the moment, but couldn't find anything in the
git tree that looked like it was likely to have fixed this.
Any suggestions for where in the code to look and try to debug this?
--
Len Sorensen
reply other threads:[~2015-05-12 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150512184341.GO24389@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--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).