From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] eia overruns at 115k baud...
Date: Thu, 18 Sep 2003 11:54:48 -0400 [thread overview]
Message-ID: <34c61bd8a1c16622d30fd58689593db6@plan9.bell-labs.com> (raw)
In-Reply-To: <20030918152533.20877.qmail@g.bio.cse.psu.edu>
On Thu Sep 18 11:26:34 EDT 2003, schwartz@bio.cse.psu.edu wrote:
> | Shouldn't be, I use 115k serial ports all the time. Sure the fifo's
> | are on? Sure they are at 16? Look at the uart code.
>
> We talked about this a few months ago... at that time the uart was
> definately getting overruns, but we decided it was ok because the network
> layer retried the few lost packets automatically.
I don't remember that being the conclusion at all.
prev parent reply other threads:[~2003-09-18 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 10:05 steve.simon
2003-09-18 15:10 ` David Presotto
2003-09-18 15:25 ` Scott Schwartz
2003-09-18 15:54 ` jmk [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=34c61bd8a1c16622d30fd58689593db6@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).