From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Trolle Selander <trolle.selander@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] iommu-remote: Fix lost serial TX interrupts. Report receive overruns.
Date: Wed, 03 Mar 2010 16:07:17 -0700 [thread overview]
Message-ID: <4B8EEBA5.4090005@scsiguy.com> (raw)
In-Reply-To: <515922b51003031052v422b98eauf82c4552b95d8dd7@mail.gmail.com>
On 3/3/2010 11:52 AM, Trolle Selander wrote:
> On Thu, Jan 28, 2010 at 6:26 PM, Justin T. Gibbs <gibbs@scsiguy.com> wrote:
>> This patch corrects emulation errors in QEMU's 16550 uart emulation,
>> which cause compatibility issues with FreeBSD's uart(9) driver.
...
> I'm assuming the overrun bugs were only triggered when the uart was
> put in loopback mode?
Yes. The FreeBSD driver puts the uart into loopback mode to probe the
size of the device's FIFO.
--
Justin
prev parent reply other threads:[~2010-03-03 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 23:26 [PATCH] iommu-remote: Fix lost serial TX interrupts. Report receive overruns Justin T. Gibbs
2010-01-29 14:48 ` Ian Jackson
2010-01-29 15:30 ` Justin T. Gibbs
2010-02-01 16:34 ` Ian Jackson
2010-03-03 18:52 ` Trolle Selander
2010-03-03 23:07 ` Justin T. Gibbs [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=4B8EEBA5.4090005@scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=trolle.selander@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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).