The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Thu, 19 Dec 2019 17:54:09 +1100	[thread overview]
Message-ID: <CAKzdPgznw+fzOdZTJwVv3Vb0a3MnEBoJfjtWz2fayPjrg3UKYg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W65VT-+nXPQtt6iiEPoKtZdxNjnzgxwiW9_ODgJYzbUMw@mail.gmail.com>

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

The Gnot had a 68040 (which had an MMU that paged properly) and an INCON
interface, which was a kind of Datakit for the home. Twisted pair. Half a
megabit if I remember right, but I probably don't.

Two bits per pixel. The "render extension" in X Windows originated there,
after an epiphany I had while watching Hoop Dreams. True story.

The MIPS machine you refer to was called a Magnum, made by somebody for
Microsoft as a porting engine for Windows to non-Intel.

-rob


On Thu, Dec 19, 2019 at 4:13 PM Dan Cross <crossd@gmail.com> wrote:

> On Wed, Dec 18, 2019 at 7:27 PM Rob Pike <robpike@gmail.com> wrote:
>
>> [snip]
>>
> 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.
>>
>
> The first time I saw a terminal of that lineage, it was a gnot (Gnot?
> GNOT?) running Plan 9; this would likely have been 1993 or 1994; I was in
> high school and visited a college-student friend of mine who was interning
> at the labs and Dennis Ritchie had one on his desk. As an aside, he kindly
> spared me a few minutes; I confess I was too star-struck and embarrassed to
> ask him to autograph my copy of K&R that I had brought along. Dennis was a
> kind, humble person and I was always quite struck by that in comparison to
> some other academic and industry super-stars I've met.
>
> Anyway, my question is what was the evolutionary story of the gnot? I
> recall being told that it had a 68020, a datakit interface, and some amount
> of RAM that was small but non-trivial; perhaps 4MB? It seemed clearly
> evolved from the series of earlier terminals presently under discussion.
>
> And the next step in the evolution was a MIPS-based terminal; I can't
> recall the name, though.
>
>         - Dan C.
>
>

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

  reply	other threads:[~2019-12-19  6:54 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
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 [this message]
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=CAKzdPgznw+fzOdZTJwVv3Vb0a3MnEBoJfjtWz2fayPjrg3UKYg@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=crossd@gmail.com \
    --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).