public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Raphael Hertzog <hertzog@debian.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid serial port buffer overruns?
Date: Wed, 16 Aug 2006 16:42:22 +0200	[thread overview]
Message-ID: <20060816144221.GO15015@harddisk-recovery.com> (raw)
In-Reply-To: <44E32D19.3090405@shaw.ca>

On Wed, Aug 16, 2006 at 08:35:05AM -0600, Robert Hancock wrote:
> Raphael Hertzog wrote:
> >(Please CC me when replying)
> >
> >Hello,
> >
> >While using Linux on low-end (semi-embedded) hardware (386 SX 40Mhz, 8Mb
> >RAM), I discovered that Linux on that machine would suffer from serial
> >port buffer overruns quite easily if I use a baudrate high enough (I start
> >loosing bytes at >19200 bauds and I would like to make it reliable up to 
> >115 kbauds). I check if overruns are happening with
> >/proc/tty/driver/serial ("oe" field).
> 
> What kind of serial port are you using? If it's an unbuffered 8250-type 
> port, it will NEVER be reliable at higher baud rates. You want a 16550 
> (or better) port.

I've run a cable modem connection at 115k2 over a 16450 UART on a
386DX40 for years. The tricks were:

- hdparm -u 1 /dev/hda
- play with IRQ priorities in such a way that the serial port UART was
  handled first (there used to be a kernel module to accomplish that in
  old debian releases)


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2006-08-16 14:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.AByCsBI8k71hMVzCyQVimrLiDU4@ifi.uio.no>
2006-08-16 14:35 ` How to avoid serial port buffer overruns? Robert Hancock
2006-08-16 14:42   ` Erik Mouw [this message]
2006-08-16 10:45 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
2006-08-16 23:28               ` 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

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=20060816144221.GO15015@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=hancockr@shaw.ca \
    --cc=hertzog@debian.org \
    --cc=linux-kernel@vger.kernel.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