From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] eia overruns at 115k baud...
Date: Thu, 18 Sep 2003 11:05:44 +0100 [thread overview]
Message-ID: <948281b86b66dede835fe0b44ba0c92b@yourdomain.dom> (raw)
Hi,
This is not really surprising but I get serial port overruns
on /dev/eia1 when reading at 115k baud (450Mhz PII).
Unfortunately I need this rate to talk to the bootstrap the
embedded systems we use here, and big xilinxes have BIG image files.
The serial interface does not use any handshaking, though it is a stop and
wait protocol and the packest are only 512 bytes, so that size of RX buffer
should be sufficent.
Just before I start hacking, anyone know of any inherent limitations
in the which might scupper me? I guess I need 1ms interrupt latency
(16 byte FIFOs), is this too much to expect from a multitasking kernel?
-Steve
next reply other threads:[~2003-09-18 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 10:05 steve.simon [this message]
2003-09-18 15:10 ` David Presotto
2003-09-18 15:25 ` Scott Schwartz
2003-09-18 15:54 ` jmk
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=948281b86b66dede835fe0b44ba0c92b@yourdomain.dom \
--to=steve.simon@snellwilcox.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).