public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: root@chaos.analogic.com
Cc: Tigran Aivazian <tigran@veritas.com>,
	David Schwartz <davids@webmaster.com>,
	Justin Piszcz <jpiszcz@hotmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Microcode Question
Date: Mon, 22 Mar 2004 11:51:47 -0500	[thread overview]
Message-ID: <405F19A3.20001@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0403221057400.17797@chaos>



Richard B. Johnson wrote:

> 
> ALL instructions are performed by the microcode. 

The Z80 had no microcode.  It was completely hard-wired.

As I understand it, it's pretty much an ancient idea to do "everything" 
by microcode.  Only certain very complex instructions are done by microcode.

On the other hand, as I said before, it's not unreasonable for lookup 
tables to be involved in instruction decoding.


  reply	other threads:[~2004-03-22 16:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 16:40 Linux Kernel Microcode Question Justin Piszcz
2004-03-18 16:59 ` Dave Jones
2004-03-18 17:13   ` David Schwartz
2004-03-19 17:27     ` Tigran Aivazian
2004-03-19 23:16       ` David Schwartz
2004-03-22 11:55         ` Tigran Aivazian
2004-03-22 15:51       ` Timothy Miller
2004-03-22 15:40         ` Tigran Aivazian
2004-03-22 16:19           ` Timothy Miller
2004-03-22 19:14           ` David Schwartz
2004-03-22 20:58             ` John Bradford
2004-03-22 16:13         ` Richard B. Johnson
2004-03-22 16:51           ` Timothy Miller [this message]
2004-03-22 17:14             ` Richard B. Johnson
2004-03-18 16:59 ` Richard B. Johnson
2004-03-18 17:07   ` Robert Love
2004-03-19  0:16   ` Bill Davidsen
2004-03-19 12:56     ` Richard B. Johnson
2004-03-18 22:20 ` Tigran Aivazian
  -- strict thread matches above, loose matches on Subject: below --
2004-03-18 17:19 Nakajima, Jun

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=405F19A3.20001@techsource.com \
    --to=miller@techsource.com \
    --cc=davids@webmaster.com \
    --cc=jpiszcz@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=tigran@veritas.com \
    /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