The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <>
Subject: Re: [TUHS] Encoding an ISA: Random Logic vs. Control Stores
Date: Tue, 30 Nov 2021 15:39:54 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Arnold,

> 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.

I'm more used to ‘hard-wired’ logic versus ‘micro-programmed’ for
microcode but random logic in a known term in this context:

    Random logic is a semiconductor circuit design technique that
    translates high-level logic descriptions directly into hardware
    features such as AND and OR gates.  The name derives from the fact
    that few easily discernible patterns are evident in the arrangement
    of features on the chip and in the interconnects between them.

Cheers, Ralph.

  reply	other threads:[~2021-11-30 15:43 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
2021-11-30 15:39     ` Ralph Corderoy [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).