From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] CR delay for VT05
Date: Wed, 29 Jul 2020 20:56:55 -0400 [thread overview]
Message-ID: <CAC20D2PeuR6ARbmiO6qOB5bMOrQufppcJv-s_ye6e05OxAim+Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007300919210.76447@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
You wish. VT05 was designed in 71 - straight TTL, no microprocessor. Same
for the VT-52. First micro was an 8085A in the VT1XX
Prints are: http://www.pdp8.net/query_docs/query_all.html
On Wed, Jul 29, 2020 at 7:25 PM Dave Horsfall <dave@horsfall.org> wrote:
> On Mon, 20 Jul 2020, Richard Tobin wrote:
>
> > Why would the VT05 (a VDU) need a delay for carriage return? I can just
> > about imagine that it might need one for linefeed if it shifted the
> > characters in memory.
>
> Given that the VT05 (shudder!) is broken in so many others ways e.g. 20x72
> screen, sends upper-case only unless you flip an internal switch, etc, I'm
> not surprised that it would also need a CR delay...
>
> Primitive firmware?
>
> -- Dave
>
[-- Attachment #2: Type: text/html, Size: 1378 bytes --]
next prev parent reply other threads:[~2020-07-30 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 23:32 Richard Tobin
2020-07-20 4:28 ` Random832
2020-07-29 23:23 ` Dave Horsfall
2020-07-30 0:56 ` Clem Cole [this message]
2020-07-30 16:42 ` Paul Winalski
2020-08-12 2:09 ` Dave Horsfall
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=CAC20D2PeuR6ARbmiO6qOB5bMOrQufppcJv-s_ye6e05OxAim+Q@mail.gmail.com \
--to=clemc@ccc.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/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).