From: Tony Finch <dot@dotat.at>
To: Clem Cole <clemc@ccc.com>
Cc: COFF <coff@minnie.tuhs.org>
Subject: Re: [COFF] [TUHS] Genix / early 80's VM variants
Date: Mon, 10 May 2021 19:35:32 +0100 [thread overview]
Message-ID: <c9a1b840-7531-1fde-fcb0-c81b8ffda37@dotat.at> (raw)
In-Reply-To: <CAC20D2NuW3U_zHwkxm7wWTjApLtB2hTtq_N_mPYe2RMS0eATtQ@mail.gmail.com>
[ COFF not TUHS ]
Clem Cole <clemc@ccc.com> wrote:
> On Sun, May 9, 2021 at 3:58 PM Larry McVoy <lm@mcvoy.com> wrote:
>
> > National couldn't get it together to produce bug free chips or maybe
> > we'd all be running that, pretty nice architecture (in theory).
>
> I've always wondered if a Nat Semi NS32016 based system running in a PC/AT
> form factor had appeared that was priced like a PC/AT if that might have
> had a chance.
Acorn Computers made an odd machine consisting of a BBC micro with a 32016
second processor in a box. (It didn't run a unix-like OS, I'm afraid.) The
32016 was one of the CPUs that inspired the ARM, because its performance
was so terrible: it was not able to make good use of the available memory
bandwidth. (There wasn't a 68000 second processor because its interrupt
latency was too bad to drive the "tube" interface.)
http://chrisacorns.computinghistory.org.uk/Computers/ACW.html
https://en.wikipedia.org/wiki/Acorn_Computers#New_RISC_architecture
Tony.
--
f.anthony.n.finch <dot@dotat.at> https://dotat.at/
Malin, Southeast Hebrides: Cyclonic 4 to 6. Slight or moderate in
southeast, moderate or rough in northwest. Showers. Good, occasionally
poor.
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
parent reply other threads:[~2021-05-10 18:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAC20D2NuW3U_zHwkxm7wWTjApLtB2hTtq_N_mPYe2RMS0eATtQ@mail.gmail.com>]
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=c9a1b840-7531-1fde-fcb0-c81b8ffda37@dotat.at \
--to=dot@dotat.at \
--cc=clemc@ccc.com \
--cc=coff@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).