From: Rob Pike <robpike@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: DMD 5620 simulator
Date: Tue, 13 Sep 2022 11:58:38 +1000 [thread overview]
Message-ID: <CAKzdPgz_0AFU259C1_1mW8QmWKJu31GbcftaHmo+J2-U1XK+-Q@mail.gmail.com> (raw)
In-Reply-To: <20220913015316.GM9175@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
Some time ago, Greg Christie, then at Apple, booted up a 3B2 with a 5620
attached and invited me to play with it. Now _that_ was a trip down memory
lane. (The 3B2, maybe not so much.)
It was a reward for an interview with him, recorded on video, about the
early days of 2d graphics as I saw them, for a course for employees. But
being Apple, even though it was 0% proprietary, it will never see the light
of day.
-rob
On Tue, Sep 13, 2022 at 11:53 AM Larry McVoy <lm@mcvoy.com> wrote:
> This looks like some really nice work. I used a BLIT at UW Madison
> and loved it, it was way more useful than a terminal and way less
> fuss than a full blown windowing system. Felt like the knee of the
> curve. All of that over a serial line, that's impressive.
>
> I dunno, but I bet that Rob trys it out just for a trip down memory
> lane.
>
> On Mon, Sep 12, 2022 at 04:25:50PM -0700, Seth Morabito wrote:
> > Hello all,
> >
> > I've recently been improving the AT&T/Teletype DMD 5620 simulator I
> wrote a few years ago. It can now run either the 8;7;3 or 8;7;5 firmware.
> It also now supports executing a local shell or connecting directly to a
> physical or virtual tty device. It runs natively on Linux or macOS with X11
> or Wayland, but I would love help creating a Windows version if you're a
> Windows programmer (I am an occasional Windows user, but I am not at all
> knowledgeable about Windows programming).
> >
> > Full details are available here:
> https://loomcom.com/3b2/dmd5620_emulator.html
> >
> > The source code is here: https://github.com/sethm/dmd_gtk
> >
> > Many thanks go to my friend Sark (@crtdude on Twitter) for tracking down
> the 8;7;3 firmware and dumping it for me. I'd also like to thank Mike
> Haertel for helping find bugs, providing feedback, and inspiring me to get
> it working with Research Unix in addition to SVR3.
> >
> > Feedback, bug reports, and pull requests are all welcome!
> >
> > -Seth
> > --
> > Seth Morabito
> > Poulsbo, WA
> > web@loomcom.com
>
> --
> ---
> Larry McVoy Retired to fishing
> http://www.mcvoy.com/lm/boat
>
[-- Attachment #2: Type: text/html, Size: 3273 bytes --]
next prev parent reply other threads:[~2022-09-13 2:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 23:25 [TUHS] " Seth Morabito
2022-09-13 1:53 ` [TUHS] " Larry McVoy
2022-09-13 1:58 ` Rob Pike [this message]
2022-09-13 2:12 ` Larry McVoy
2022-09-13 13:01 ` Clem Cole
2022-09-14 0:23 ` Rob Pike
2022-09-14 0:33 ` Larry McVoy
2022-09-14 0:43 ` Rich Salz
2022-09-13 19:21 ` Paul Guertin
2022-09-13 22:29 ` Joseph Holsten
2022-09-13 23:35 ` Larry McVoy
2022-09-14 3:55 ` Joseph Holsten
2022-09-14 16:09 ` Kevin Bowling
2022-09-14 0:44 ` Steve Nickolas
2022-09-14 0:47 ` joe mcguckin
2022-09-14 3:10 ` Seth Morabito
2022-09-14 3:40 ` Warner Losh
2022-09-14 7:48 ` Lars Brinkhoff
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=CAKzdPgz_0AFU259C1_1mW8QmWKJu31GbcftaHmo+J2-U1XK+-Q@mail.gmail.com \
--to=robpike@gmail.com \
--cc=lm@mcvoy.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).