From: drb at msu.edu (Dennis Boone)
Subject: [COFF] 52-pin D-Sub?
Date: Fri, 28 Feb 2020 17:05:31 -0500 [thread overview]
Message-ID: <20200228220532.17F741ADFAF@yagi.h-net.msu.edu> (raw)
In-Reply-To: (Your message of Sat, 29 Feb 2020 08:58:40 +1100.) <alpine.BSF.2.21.9999.2002290850410.1121@aneurin.horsfall.org>
> using the secondary pins as well.
Best I could tell, the major intended purpose of the secondary circuits
was to implement autodialer, especially when those handshaking signals
on the primary were down because there was no connection, so you
couldn't do anything through them yet.
Was there anything else in mind during the spec process?
De
next prev parent reply other threads:[~2020-02-28 22:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 23:37 athornton
2020-02-28 0:04 ` dave
2020-02-28 1:37 ` stewart
2020-02-28 2:12 ` athornton
2020-02-28 4:12 ` dave
2020-02-28 4:18 ` dave
2020-02-28 14:11 ` clemc
2020-02-28 14:34 ` athornton
2020-02-28 21:23 ` dave
2020-02-28 16:35 ` krewat
2020-02-28 21:28 ` dave
2020-02-28 21:44 ` clemc
2020-02-28 21:58 ` dave
2020-02-28 22:20 ` clemc
2020-02-28 23:22 ` pechter
2020-02-29 13:12 ` emu
2020-02-29 15:45 ` krewat
2020-02-29 15:49 ` clemc
2020-02-28 22:38 ` pechter
2020-02-28 22:05 ` drb [this message]
2020-02-28 22:28 ` clemc
2020-02-28 22:26 ` pechter
2020-02-28 22:36 ` clemc
2020-02-28 23:40 ` pechter
2020-02-29 16:52 ` clemc
2020-02-28 23:54 ` pechter
2020-02-29 9:59 rudi.j.blom
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=20200228220532.17F741ADFAF@yagi.h-net.msu.edu \
--to=coff@minnie.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).