From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Paul Fulghum <paulkf@microgate.com>,
Raphael Hertzog <hertzog@debian.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid serial port buffer overruns?
Date: Thu, 17 Aug 2006 00:19:26 +0100 [thread overview]
Message-ID: <20060816231926.GC12407@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1155770107.8796.14.camel@mindpipe>
On Wed, Aug 16, 2006 at 07:15:06PM -0400, Lee Revell wrote:
> On Thu, 2006-08-17 at 00:10 +0100, Russell King wrote:
> > MIDI uses its own driver - sound/drivers/serial-u16550.c. My guess
> > is there's something in the system starving interrupt servicing.
> > Serial is very sensitive to that, and increases in other system
> > latencies tends to have an adverse impact on serial.
>
> Have you seen many other reports of serial working reliably in 2.4 but
> not in 2.6? Right now this is the only clue I have to go on...
There have been one or two, but the above is basically as far as I've
got. Unfortunately, I don't have any machines slow enough (or maybe
with the right hardware) to exhibit the problem.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-08-16 23:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 10:45 How to avoid serial port buffer overruns? Raphael Hertzog
2006-08-16 14:31 ` Lennart Sorensen
2006-08-16 14:57 ` Raphael Hertzog
2006-08-16 18:44 ` Lee Revell
2006-08-16 19:23 ` Paul Fulghum
2006-08-16 21:12 ` Lee Revell
2006-08-16 22:24 ` Paul Fulghum
2006-08-16 23:10 ` Russell King
2006-08-16 23:15 ` Lee Revell
2006-08-16 23:19 ` Russell King [this message]
2006-08-16 23:28 ` Lee Revell
2006-08-17 0:15 ` R: " Giampaolo Tomassoni
2006-08-18 8:48 ` Giampaolo Tomassoni
2006-08-18 17:00 ` Lee Revell
2006-08-18 17:04 ` Russell King
2006-08-18 17:30 ` Lee Revell
2006-08-18 18:34 ` Russell King
2006-08-18 18:52 ` Lee Revell
2006-08-18 19:01 ` Russell King
2006-08-18 19:07 ` Russell King
2006-08-18 19:09 ` Lee Revell
2006-08-17 9:20 ` Alan Cox
2006-08-17 9:28 ` Russell King
2006-08-17 11:57 ` Alan Cox
2006-08-17 13:29 ` Paul Fulghum
2006-08-17 15:48 ` Raphael Hertzog
2006-08-17 16:10 ` Raphael Hertzog
2006-08-17 16:40 ` Paul Fulghum
2006-08-18 19:31 ` Lee Revell
2006-08-23 12:45 ` Raphael Hertzog
[not found] <fa.AByCsBI8k71hMVzCyQVimrLiDU4@ifi.uio.no>
2006-08-16 14:35 ` Robert Hancock
2006-08-16 14:42 ` Erik Mouw
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=20060816231926.GC12407@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=hertzog@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=rlrevell@joe-job.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