Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] 52-pin D-Sub?
Date: Fri, 28 Feb 2020 09:11:26 -0500	[thread overview]
Message-ID: <CAC20D2Or=9DnR287GottTO=1hnZyH4F6TLyipHhkqtepquKVdQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002281517180.1121@aneurin.horsfall.org>

Adam/Dave,

For whatever's it's worth, in PC/AT ISA bus times, at least one of the
serial port vendors (RocketPort was the vendor IIRC), used a DB-52P
connector, that connected to an interesting 'tail' which had 8 DB25P
connected to the DB25-S at the other end.   This allowed 6 data conductors
(RCV/XMT/RTS/CTS/CD/DTR) * 8 ports, plus 6 grounds which again IIRC they
interspersed among the remaining 6 ground pins.

What I remember is that it was this specific board that was one of only a
handful serial boards[1] that could run UNIX properly and hang Trailblazer
modems off of it because they not only fully pinned, but they had
single-chip custom USART with a good bit of buffering and hardware-based
RTS/CTS flow control.  I think I may still have one somewhere, as I saw the
cable for it when I was looking for something else over the Christmas
holidays.

[1] The original PC/AT used the NS8250 UART with no input buffering, which
went through a couple of generations, eventually begat the *550 version and
had I think an 8 character input buffer.  But IIRC none of them had
hardware flow control.   I forget the # now, Moto made a nice dual UART
with 16 chars of input buffering, that many of us on Unix workstation
business used, but when we moved to BSD 386 and Linux, we were stuck with
PC hardware, which had a particularly hard time with things like the
Trailblazer  (which was the modem of choice for UUCP).

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200228/fa9671c3/attachment.html>


  reply	other threads:[~2020-02-28 14:11 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 [this message]
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
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='CAC20D2Or=9DnR287GottTO=1hnZyH4F6TLyipHhkqtepquKVdQ@mail.gmail.com' \
    --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).