Article View: comp.arch
Article #11402Re: DEC Alpha architecture issues
From: Donald Lindsay
Date: Sun, 22 Nov 1992 17:47
Date: Sun, 22 Nov 1992 17:47
14 lines
1262 bytes
1262 bytes
andrew@megadata.mega.oz.au (Andrew McRae) writes: >If it looks like microcode, smells like microcode ... Why call it PALcode? Because it doesn't even vaguely resemble microcode. - PALcode is fetched from the I-cache, not from ROM. - PALcode is decoded by the normal decoder, as opposed to to microcode, which is often a raw mask over a processor's internal control lines. - Microcode is usually in charge of detailed sequencing/timing of e.g. register writebacks. PALcode has no concept of this, except for some implementation-specific rules like "if you set this TLB control register, then the TLB mode will change one clock later". -- Don D.C.Lindsay Carnegie Mellon Computer Science
Technical Details
Message-ID:
<By4pEI.8r5.2@cs.cmu.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!lindsayReferences:
<1992Nov20.064529.20293@nntpd.lkg.dec.com> <1992Nov22.043852.764@megadata.mega.oz.au>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!lindsay From: lindsay+@cs.cmu.edu (Donald Lindsay) Newsgroups: comp.arch Subject: Re: DEC Alpha architecture issues Message-ID: <By4pEI.8r5.2@cs.cmu.edu> Date: 22 Nov 92 17:47:06 GMT Article-I.D.: cs.By4pEI.8r5.2 References: <1992Nov20.064529.20293@nntpd.lkg.dec.com> <1992Nov22.043852.764@megadata.mega.oz.au> Sender: news@cs.cmu.edu (Usenet News System) Organization: School of Computer Science, Carnegie Mellon Lines: 14 Nntp-Posting-Host: gandalf.cs.cmu.edu