The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Origins of the frame buffer device
Date: Mon, 6 Mar 2023 07:43:48 +1100	[thread overview]
Message-ID: <CAKzdPgzMyRYyB3-V8vtrCr97zc=5R8h4rTxxogYuvxZXx14NxA@mail.gmail.com> (raw)
In-Reply-To: <20230305185202.91B7B18C08D@mercury.lcs.mit.edu>

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

There was a Three Rivers Graphic Wonder (a vector display) on the
University of Toronto PDP-11/45 in 1975, maybe 1974. There wasn't a frame
buffer until Dave Tennenhouse built one around 1978 - not sure of that
date, maybe a little later
.
256x256, 8 bits per pixel, or 65kilobytes, the full data address space of
the PDP-11.

-rob


On Mon, Mar 6, 2023 at 5:52 AM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Kenneth Goodwin
>
>     > The first frame buffers from Evans and Sutherland were at University
> of
>     > Utah, DOD SITES and NYIT CGL as I recall.
>     > Circa 1974 to 1978.
>
> Were those on PDP-11's, or PDP-10's? (Really early E+S gear attached to
> PDP-10's; '74-'78 sounds like an interim period.)
>
>           Noel
>
>

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

  reply	other threads:[~2023-03-05 20:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 18:52 Noel Chiappa
2023-03-05 20:43 ` Rob Pike [this message]
2023-03-06 10:43   ` Jonathan Gray
2023-03-07  1:21 ` Kenneth Goodwin
2023-03-08  5:43 ` Lars Brinkhoff
2023-03-09 23:24   ` emanuel stiebler
2023-03-10  1:44     ` Lawrence Stewart
  -- strict thread matches above, loose matches on Subject: below --
2023-03-06 23:16 Norman Wilson
2023-03-06 23:24 ` Larry McVoy
2023-03-07 12:08   ` arnold
2023-03-07 16:42   ` Theodore Ts'o
2023-03-05 15:01 [TUHS] " Paul Ruizendaal via TUHS
2023-03-05 17:29 ` [TUHS] " Grant Taylor via TUHS
2023-03-05 18:25 ` Kenneth Goodwin
2023-03-06  8:51   ` Paul Ruizendaal via TUHS
2023-03-06  8:57     ` Rob Pike
2023-03-06 11:09       ` Henry Bent
2023-03-06 16:02         ` Theodore Ts'o
2023-03-06 22:47       ` Paul Ruizendaal via TUHS
2023-03-06 23:10         ` Rob Pike
2023-03-08 12:53           ` Paul Ruizendaal
2023-03-08 14:23             ` Dan Cross
2023-03-08 15:06               ` Paul Ruizendaal
2023-03-08 19:35                 ` Dan Cross
2023-03-08 16:55               ` Theodore Ts'o
2023-03-08 17:46                 ` Clem Cole
2023-03-08 17:45               ` Clem Cole
2023-03-08 18:12                 ` segaloco via TUHS
2023-03-08 18:21                   ` Larry McVoy
2023-03-08 18:43                     ` Kenneth Goodwin
2023-03-08 18:45                     ` Steffen Nurpmeso
2023-03-08 22:44                     ` Clem Cole
2023-03-09 14:42                 ` Paul Winalski
2023-03-06 23:20         ` segaloco via TUHS
2023-03-07  1:24     ` Kenneth Goodwin
2023-03-08  3:07     ` Rob Gingell
2023-03-08 12:51       ` Paul Ruizendaal via TUHS
2023-03-08 13:05         ` Warner Losh
2023-03-08 13:17         ` Arno Griffioen via TUHS
2023-03-07  1:54 ` Kenneth Goodwin

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='CAKzdPgzMyRYyB3-V8vtrCr97zc=5R8h4rTxxogYuvxZXx14NxA@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).