home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!spool.mu.edu!umn.edu!noc.msc.net!news.stolaf.edu!lars.acc-admin.stolaf.edu!johnsonm
- From: johnsonm@lars.acc-admin.stolaf.edu (Michael K. Johnson)
- Subject: Re: Serial communications problems
- In-Reply-To: tytso@ATHENA.MIT.EDU's message of Tue, 15 Dec 1992 02:39:31 GMT
- Message-ID: <1992Dec15.040444.16442@news.stolaf.edu>
- Sender: news@news.stolaf.edu
- Organization: St. Olaf College; Northfield, MN USA
- References: <1992Dec15.023931.6220@athena.mit.edu>
- Date: Tue, 15 Dec 1992 04:04:44 GMT
- Lines: 18
-
-
- In article <1992Dec15.023931.6220@athena.mit.edu> tytso@ATHENA.MIT.EDU (Theodore Ts'o) writes:
- From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
- Date: Sun, 13 Dec 1992 04:34:23 GMT
-
- You're a bit too pessimistic here. I'm using such a driver to run all
- four COM ports and it does 2400 bps with a 16450 and 19200 bps with a
- 16550A. 19200 bps gets a bit unreliable under load, but it's still
- acceptable for Zmodem. I'm polling at 300 Hz and it doesn't lower
- system performance very noticeably.
-
- Is this on Linux? How are you polling at 300Hz, when the system clock
- ticks at 100Hz?
-
- It's really not that hard to reprogram the clock for 300 Hz, and then
- call do_timer() from your polling interrupt every third call.
-
- michaelkjohnson
-