From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Andrey Korolyov <andrey@xdel.ru>,
Kirill Batuzov <batuzovk@ispras.ru>,
Markus Armbruster <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Serial: possible hang during intensive interaction over the console
Date: Thu, 11 Dec 2014 20:35:31 +0100 [thread overview]
Message-ID: <5489F203.8050809@redhat.com> (raw)
In-Reply-To: <CAFEAcA9neVahXifSBi153YgrXOPnLF2qp_LffTk2Afg8Wo8rvA@mail.gmail.com>
On 11/12/2014 16:06, Peter Maydell wrote:
> An abstraction of that from the specifics of the PC's serial port
> might be nice, yes. (omap_uart.c has to jump through some ugly hoops
> currently, with more ugliness in the out-of-tree omap3 extensions.)
> However I don't think it makes sense to force all serial port
> device models to go through it -- not all the world is a 16550A
> and some UARTs simply are different.
No, definitely not. There's still qemu-char, this would just be an
abstraction providing useful stuff like baud rates and flow control.
Paolo
prev parent reply other threads:[~2014-12-11 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 10:35 [Qemu-devel] Serial: possible hang during intensive interaction over the console Andrey Korolyov
2014-09-04 9:46 ` Kirill Batuzov
2014-09-04 10:00 ` Andrey Korolyov
2014-09-04 13:33 ` Kirill Batuzov
2014-09-04 16:03 ` Andrey Korolyov
2014-09-05 17:45 ` Andrey Korolyov
2014-09-09 15:28 ` Kirill Batuzov
2014-09-09 15:44 ` Andrey Korolyov
2014-12-11 14:56 ` Paolo Bonzini
2014-12-11 15:06 ` Peter Maydell
2014-12-11 19:35 ` Paolo Bonzini [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=5489F203.8050809@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrey@xdel.ru \
--cc=armbru@redhat.com \
--cc=batuzovk@ispras.ru \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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).