From: Arthur Krewat <krewat@kilonet.net>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 68k prototypes & microcode
Date: Thu, 4 Feb 2021 10:47:03 -0500 [thread overview]
Message-ID: <09f134dd-ed70-5ff5-08d3-70c9a4ff97e3@kilonet.net> (raw)
In-Reply-To: <20210204013356.GA16541@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On 2/3/2021 8:33 PM, Larry McVoy wrote:
>> The 68K always reminded me of the VAX.
> I'm not sure if that is a compliment or not.
Neither, more of an observation than anything.
Post/pre decrement/increment, 32-bit everything, it was an easy move,
mentally, from VAX to 68K. I cut my teeth on a PDP-10, but also VAX, and
a sprinkling of microprocessors such as the 8080, Z80, 6502 and of
course, 8088/86.
Back around the mid 80's, a friend and I built a 68020 prototype
computer from spare parts, all wire-wrapped, fast static RAM (it was
free), and I wrote a cross-assembler in C (on a 80386 PC) and we went to
town. And then, as they say, life happened. It was much easier to get
access to, or take home, powerful enough computers that we didn't need
to build our own. My friend still has the thing. I still have the
cross-assembler too, but sadly no actual code I wrote at the time. It
would have been worth a laugh or two ;)
I still have a Sun 3/280 laying around here somewhere...
art k.
[-- Attachment #2: Type: text/html, Size: 1518 bytes --]
next prev parent reply other threads:[~2021-02-04 15:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 10:49 [TUHS] AT&T 3B1 - Emulation available Arnold Robbins
2021-01-29 13:49 ` Ronald Natalie
2021-01-29 14:37 ` Clem Cole
2021-01-31 7:57 ` arnold
2021-01-31 8:41 ` Rich Morin
2021-02-03 7:53 ` emanuel stiebler
2021-02-03 7:59 ` arnold
2021-02-03 8:53 ` Ed Bradford
2021-02-03 8:58 ` arnold
2021-02-03 10:13 ` Ed Bradford
2021-02-03 14:58 ` Clem Cole
2021-02-03 15:33 ` Henry Bent
2021-02-03 16:53 ` Clem Cole
2021-02-04 0:41 ` [TUHS] 68k prototypes & microcode John Gilmore
2021-02-04 0:52 ` Al Kossow
2021-02-04 1:10 ` Arthur Krewat
2021-02-04 1:33 ` Larry McVoy
2021-02-04 1:47 ` Al Kossow
2021-02-04 1:57 ` Al Kossow
2021-02-04 7:23 ` Arno Griffioen
2021-02-04 11:28 ` Toby Thain
2021-02-04 15:47 ` Arthur Krewat [this message]
2021-02-04 16:03 ` emanuel stiebler
2021-02-04 21:55 ` Dave Horsfall
2021-02-04 22:11 ` Steve Nickolas
2021-02-04 22:39 ` Adam Thornton
2021-02-04 22:47 ` Henry Bent
2021-02-05 14:42 ` Michael Parson
2021-02-04 22:56 ` Richard Salz
2021-02-04 23:14 ` Steve Nickolas
2021-02-04 1:35 ` Clem Cole
2021-02-04 2:18 ` Dave Horsfall
2021-02-04 15:53 ` Arthur Krewat
2021-02-05 2:16 ` Dave Horsfall
2021-02-05 2:53 ` Larry McVoy
2021-02-04 1:14 ` Clem Cole
2021-02-04 1:20 ` Clem Cole
2021-02-04 14:56 ` John Cowan
2021-02-03 15:20 ` [TUHS] AT&T 3B1 - Emulation available emanuel stiebler
2021-02-03 16:48 ` Doug McIntyre
2021-02-03 10:46 ` emanuel stiebler
2021-02-03 11:13 ` arnold
2021-02-05 12:44 ` Sergio Pedraja
2021-02-07 7:32 ` arnold
2021-02-17 16:07 ` emanuel stiebler
2021-02-17 22:00 ` Ed Carp
2021-02-17 22:14 ` Larry McVoy
2021-02-18 1:30 ` Ed Carp
2021-02-18 7:59 ` arnold
2021-02-18 18:07 ` Brad Spencer
2021-02-13 1:06 [TUHS] 68k prototypes & microcode Jason Stevens
2021-02-13 2:30 ` Gregg Levine
2021-02-13 4:34 Jason Stevens
2021-02-13 6:05 ` Toby Thain
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=09f134dd-ed70-5ff5-08d3-70c9a4ff97e3@kilonet.net \
--to=krewat@kilonet.net \
--cc=lm@mcvoy.com \
--cc=tuhs@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).