Article View: comp.sys.m68k.pc
Article #211Re: opcode emulation (Was: Re: 68020 in a *68010* socket?)
From: Mike Meyer, I'm in love with my ...
Date: Wed, 15 Jun 1988 13:51
Date: Wed, 15 Jun 1988 13:51
18 lines
1346 bytes
1346 bytes
>> Personaly I have never seen the 012 and do not recal even reading >> of any products using it. Maybe the 012 never made it out of sample >> phase? I recall seeing literature on an entry-level supercomputer (alliant?) that used multiple 68012s as front ends. Last time I looked, they had switched to 68020s. I vaguely recall one other product that used the '012, but nothing else about it (the only thing noteworthy was that it was using a '012 :-). My recollection of the '012 announcement is that it was just a 68010 chip with more address lines brought to the outside world, and only available in a square, ceramic, mil-spec package. Given that, there wasn't much reason to use it instead of an '010. Unless you needed that extra address space, or the RMC\ pin mentioned by Michael Galassi (the multi-processer front end makes it make sense). <mike
Technical Details
Message-ID:
<8806151351.AA14315@violet.berkeley.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!VIOLET.BERKELEY.EDU!mwmShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!VIOLET.BERKELEY.EDU!mwm From: mwm@VIOLET.BERKELEY.EDU (Mike Meyer, I'm in love with my car) Newsgroups: comp.sys.m68k.pc Subject: Re: opcode emulation (Was: Re: 68020 in a *68010* socket?) Message-ID: <8806151351.AA14315@violet.berkeley.edu> Date: 15 Jun 88 13:51:39 GMT Sender: mwm@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 17 Approved: info-68k@ucbvax.berkeley.edu