From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, ron@ronnatalie.com, pbirkel@gmail.com
Cc: eugene@soe.ucsc.edu
Subject: Re: [TUHS] Encoding an ISA: Random Logic vs. Control Stores
Date: Tue, 30 Nov 2021 08:30:02 -0700 [thread overview]
Message-ID: <202111301530.1AUFU2eC015214@freefriends.org> (raw)
In-Reply-To: <em13f2dbb4-13fd-4d28-b5f9-3ba3b7072e76@alien>
Can someone please explain why it's called "random" logic? Discrete
logic I understand (more or less), but I've not heard the term "random"
used in this context before now.
Thanks,
Arnold
"Ron Natalie" <ron@ronnatalie.com> wrote:
> Indeed, the early PDPs (10/15/20) had no microprogramming at all. Even
> the early microprogrammed ones used "random logic" to implement that.
> It would take ten years before large scale integration took over. The
> PDP-11/44 in 1979 was the last of the discrete logic CPUs.
>
>
> ------ Original Message ------
> From: pbirkel@gmail.com
> To: "'TUHS main list'" <tuhs@minnie.tuhs.org>
> Cc: "'Eugene Miya'" <eugene@soe.ucsc.edu>
> Sent: 11/30/2021 3:07:15 AM
> Subject: [TUHS] Encoding an ISA: Random Logic vs. Control Stores
>
> >I believe that the PDP-11 ISA was defined at a time when DEC was still using
> >random logic rather than a control stor
>
next prev parent reply other threads:[~2021-11-30 15:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 8:07 pbirkel
2021-11-30 15:19 ` Ron Natalie
2021-11-30 15:30 ` arnold [this message]
2021-11-30 15:39 ` Ralph Corderoy
2021-11-30 18:50 ` Jon Steinhart
2021-11-30 21:45 ` Humm
2021-11-30 23:07 ` Jon Steinhart
2021-11-30 23:18 ` Henry Bent
2021-12-01 5:00 ` Jon Steinhart
2021-12-01 6:27 ` pbirkel
2021-12-01 16:42 ` ron minnich
2021-12-01 17:08 ` Ron Natalie
2021-12-01 21:56 ` [TUHS] Encoding an ISA Warren Toomey
2021-12-01 13:59 [TUHS] Encoding an ISA: Random Logic vs. Control Stores Paul Ruizendaal
2021-12-01 14:55 Douglas McIlroy
2021-12-01 20:27 ` Jon Steinhart
2021-12-01 21:14 ` Lawrence Stewart
2021-12-01 22:09 ` Jon Steinhart
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=202111301530.1AUFU2eC015214@freefriends.org \
--to=arnold@skeeve.com \
--cc=eugene@soe.ucsc.edu \
--cc=pbirkel@gmail.com \
--cc=ron@ronnatalie.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).