The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Thu, 19 Dec 2019 11:26:47 +1100	[thread overview]
Message-ID: <CAKzdPgz37wwYfmHJ_7kZx_T=-zwNJ50PhS7r0kCpuf_F1mDkww@mail.gmail.com> (raw)
In-Reply-To: <1576714621.27293.for-standards-violators@oclsc.org>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

Your naming isn't right, although the story otherwise is accurate.

The Jerq was the original name for the 68K machines hand-made by Bart. The
name, originally coined for a fun demo of the Three Rivers Perq by folks at
Lucasfilm, was borrowed with permission by us but was considered unsuitable
by Sam Morgan as we reached out to make some industrially, by a company
(something Atlantic) on Long Island. So "Blit" was coined. The Blit name
later stuck unofficially to the DMD-5620, which was made by Teletype and,
after some upheavals, had a Western Electric BellMac 32000 CPU.

If 5620s were called Jerqs, it was an accident. All the software with that
name would be for the original, Locanthi-built and -designed 68K machines.

The sequence is thus Jerq, Blit, DMD-5620. DMD stood for dot-mapped rather
than bit-mapped, but I never understood why. It seemed a category error to
me.

-rob

[-- Attachment #2: Type: text/html, Size: 1037 bytes --]

  reply	other threads:[~2019-12-19  0:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19  0:16 Norman Wilson
2019-12-19  0:26 ` Rob Pike [this message]
2019-12-19  3:47   ` Mike Haertel
2019-12-19  6:49     ` Angelo Papenhoff
2019-12-19  5:12   ` Dan Cross
2019-12-19  6:54     ` Rob Pike
2019-12-19  8:03       ` arnold
2019-12-19 15:32       ` Chet Ramey
  -- strict thread matches above, loose matches on Subject: below --
2020-01-06 21:01 Norman Wilson
2019-12-19  9:09 Paul Ruizendaal
2019-12-15 20:45 Paul Ruizendaal
2019-12-15 21:17 ` Angelo Papenhoff
2019-12-16  6:25 ` emanuel stiebler
2019-12-16 11:06   ` Paul Ruizendaal
2019-12-17  6:04     ` emanuel stiebler
2019-12-18  3:53   ` Paul Ruizendaal
2019-12-18  4:30     ` Rob Pike
2019-12-18 10:43     ` Julius Schmidt
2019-12-18 12:11       ` Angelo Papenhoff
2019-12-18 15:53         ` Dan Cross
2019-12-18 12:19       ` Paul Ruizendaal
2019-12-19  0:20   ` Paul Ruizendaal

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='CAKzdPgz37wwYfmHJ_7kZx_T=-zwNJ50PhS7r0kCpuf_F1mDkww@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=norman@oclsc.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).