All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Hertzog <hertzog@debian.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid serial port buffer overruns?
Date: Wed, 16 Aug 2006 16:57:38 +0200	[thread overview]
Message-ID: <20060816145738.GA6575@ouaza.com> (raw)
In-Reply-To: <20060816143147.GC13641@csclub.uwaterloo.ca>

On Wed, 16 Aug 2006, Lennart Sorensen wrote:
> In my experience, the way to avoid overruns on a serial port was to use
> a buffered serial port UART (such as a 16550A for example).  I remember
> my 486 wasn't reliable about 19200 or 38400 (depending on how busy the
> cpu was) when using an 8250.  Using a 16550A based card and I could do
> 115200 without any issues since the UART had a 16 byte buffer to help
> out the system.  Unless your 386 has an add in card for the serial port,
> it almost certainly has a very crappy UART and it would be very hard to
> make it work reliably at higher speeds.

I forgot to mention the kind of UART in my mail but it is a 16650A (and
configured as such and detected as such) and I have overruns nevertheless.

bash-2.05a# cat /proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:16550A port:000003F8 irq:4 tx:31 rx:7 RTS|CTS|DTR|DSR
1: uart:16550A port:000002F8 irq:3 tx:24 rx:7 RTS|CTS|DTR|DSR

(here there's no overrun but I almost didn't use the serial port since
last reboot)

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/

  reply	other threads:[~2006-08-16 14:58 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 [this message]
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
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=20060816145738.GA6575@ouaza.com \
    --to=hertzog@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.