From: random832@fastmail.com (Random832)
Subject: [TUHS] PWB contributions
Date: Mon, 09 Nov 2015 23:11:42 -0500 [thread overview]
Message-ID: <87r3jyfq81.fsf@fastmail.com> (raw)
In-Reply-To: <alpine.NEB.2.11.1511091612300.28638@t1.m.reedmedia.net>
"Jeremy C. Reed" <reed at reedmedia.net> writes:
> By the way, I don't have experience with the CR3 control register, and
> don't really understand what it means from the hardware perspective.
If I understand correctly, it's not hardware, it's part of the kernel
tty driver. There's a two bit field in the stty flags, for selecting a
delay mode. The purpose of the delay was to allow the terminal time to
process it (i.e. to physically move the carriage, for a printing
terminal) - the kernel would wait before sending more characters.
As can be seen in tty.c (link below), CR1 caused a delay of 5 units, and
CR2 a delay of 10 units. CR3 had no meaning in the standard kernel, and
so some custom version of the kernel could have interpreted it to have
some other meaning.
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/sys/dev/tty.c
It's not clear where this was actually done. The 3BSD kernel used
CR3 to indicate that (if I read it correctly) a number of padding
characters depending on the column position should be inserted.
P.S. Somewhat confusingly, searching for "CR3" finds a page about
"control registers" of the _intel 386_, of which CR3 has something to do
with "paging" in the virtual memory sense of the word. This has nothing
to do with the topic under discussion.
next prev parent reply other threads:[~2015-11-10 4:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 1:39 Doug McIlroy
2015-11-09 1:48 ` John Cowan
2015-11-09 2:12 ` Clement T. Cole
2015-11-09 2:54 ` Win Treese
2015-11-09 2:58 ` Win Treese
2015-11-09 3:36 ` Clem cole
2015-11-09 3:51 ` Clem cole
2015-11-09 15:40 ` Dave Horsfall
2015-11-09 15:54 ` Clem Cole
2015-11-09 22:12 ` Mary Ann Horton
2015-11-09 3:38 ` Random832
2015-11-09 4:50 ` Clem cole
2015-11-09 13:58 ` Doug McIlroy
2015-11-09 14:02 ` Ronald Natalie
2015-11-09 14:44 ` John Cowan
2015-11-10 20:26 ` [TUHS] A portrait of cut(1) (was: PWB contributions) markus schnalke
2015-11-10 22:10 ` Clem Cole
2015-11-10 23:10 ` Andy Kosela
2015-11-10 23:12 ` John Cowan
2015-11-10 23:34 ` Larry McVoy
2015-11-10 23:39 ` John Cowan
2015-11-11 0:16 ` [TUHS] A portrait of cut(1) Random832
2015-11-11 12:23 ` markus schnalke
2015-11-09 22:23 ` [TUHS] PWB contributions Jeremy C. Reed
2015-11-10 4:11 ` Random832 [this message]
2015-11-09 4:44 ` Larry McVoy
2015-11-09 4:51 ` John Cowan
2015-11-09 5:07 ` Larry McVoy
2015-11-09 5:09 ` Larry McVoy
2015-11-09 5:16 ` John Cowan
2015-11-09 5:16 ` Leonardo Taccari
2015-11-09 2:14 Doug McIlroy
2015-11-09 2:32 ` John Cowan
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=87r3jyfq81.fsf@fastmail.com \
--to=random832@fastmail.com \
/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).