9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: random moving of cursor arrow
Date: Mon, 28 Jul 2003 08:47:43 +0000	[thread overview]
Message-ID: <Y-WcnYoo6KzEzr-iXTWJjA@comcast.com> (raw)
In-Reply-To: <016601c35353$10db3be0$b9844051@insultant.net>

boyd, rounin wrote:
> iirc, from the dz-kmc days you needed to manage the 'fifo' so it wouldn't
> overrun, but at the same time you needed a timer to empty it [stick on the rawq]
> so stuff just didn't get 'stuck'.

No, the problem arises when people try to set the input alarm
threshold at more than 1 character.  In the case of the DZ11
the right thing to do was to interrupt on any incoming
character and after processing (putting in the queue) wait a
tiny bit for the FIFO to trickle down then test for another
ready character, and if found don't return (context switch)
but instead go back to the start of the intr function and
process the character.  My driver did that, and on a PDP-11/34
we had a couple of dozen concurrent users of 9600bpi terminals
with great response.

I have a KMC11B sitting around, and some day I'll look into
whatever problems there might have been.  The idea of a front-
end processor was right, even if the implementation wasn't.

> how much time have i wasted with rs-232 junk?  too much.

However, it's as near to universal as one can get, even today.
I have a paper tape reader and an Apple IIGS attached to my
PCs via RS-232-C.  (The magtape is on SCSI.)


  reply	other threads:[~2003-07-28  8:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25  8:52 [9fans] " sasa
2003-07-25  8:43 ` Lucio De Re
2003-07-26 15:59   ` David Presotto
2003-07-26 16:40     ` Dan Cross
2003-07-26 16:44       ` David Presotto
2003-07-26 17:10         ` Skip Tavakkolian
2003-07-26 17:14         ` Dan Cross
2003-07-26 17:19           ` rob pike, esq.
2003-07-26 17:23           ` boyd, rounin
2003-07-28  9:00         ` matt
2003-07-26 17:10     ` boyd, rounin
2003-07-28  5:48     ` Lucio De Re
2003-07-25  9:02 ` boyd, rounin
2003-07-25  9:01   ` Lucio De Re
2003-07-25  9:08 ` Fco.J.Ballesteros
2003-07-25 14:08   ` Scott Schwartz
2003-07-25 14:35     ` UART device driver (Was: [9fans] random moving of cursor arrow) Lucio De Re
2003-07-25 14:56       ` boyd, rounin
2003-07-26  5:50       ` jmk
2003-07-28  5:36         ` Lucio De Re
2003-07-25  9:17 ` [9fans] Re: random moving of cursor arrow sasa
2003-07-25  9:24   ` sasa
2003-07-25  9:25     ` sasa
2003-07-25  9:27       ` boyd, rounin
2003-07-26  2:22         ` David Presotto
2003-07-26  8:37           ` C H Forsyth
2003-07-26  8:51             ` boyd, rounin
2003-07-28  8:47               ` Douglas A. Gwyn [this message]
2003-07-26 15:37             ` David Presotto
2003-07-26  9:59           ` Enache Adrian
2003-08-07 13:52             ` David Presotto
2003-07-26 19:01           ` Richard Miller
2003-07-28  5:26           ` Lucio De Re
2003-07-28  6:18             ` Lucio De Re
2003-07-29  3:11             ` David Presotto
2003-07-25 10:27       ` sasa
2003-08-07 14:35 David Presotto
2003-08-08 21:14 ` Enache Adrian

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=Y-WcnYoo6KzEzr-iXTWJjA@comcast.com \
    --to=dagwyn@null.net \
    --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).