Xref: utzoo comp.sys.amiga.tech:13112 comp.sys.amiga.hardware:2384
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!apple!netcom!mcmahan
From: mcmahan@netcom.UUCP (Dave Mc Mahan)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga.hardware
Subject: Re: 030 in 68000 package
Message-ID: <11485@netcom.UUCP>
Date: 3 Jul 90 05:06:07 GMT
References: <2695@zipeecs.umich.edu> <31234@cup.portal.com> <4699@munnari.oz.au>
Organization: Dave McMahan @ NetCom Services
Lines: 29


 In a previous article, krooglik@moroka4.ecr.mu.oz (Alex KROOGLIK) writes:
>
>In article <31234@cup.portal.com>, thad@cup.portal.com (Thad P Floryan) writes:
>
>> They didn't say WHY
>> they're doing this, but it seems to me that a system using the "new" 68030
>> in the 64-pin "68000" package would be a likely suspect, er... candidate.
>
> I would love to know how you could physically fit a 68030 in a 68000 package.
> For starters, the 68030 has 32 physical address lines, and using simple
> grade 2 arithmetic, that leaves 32 pins. I would love someone to tell me
> how you could add all of the complex external pin outs and ins of the 68030
> into a 64 pin DIP. Even the standard 68030 has around 114 pins (I think).

They could do it the same way that Intel slimes a 16 bit processor onto an 8
bit bus with the 8088, or the way a 68008 runs the 68000 instuction set from
a 48 pin chip.  You cut a little here, you feature-reduce a little
there.....  :-)

Seriously, I think you would have a problem with such a thing.  Lots of the
speed improvements are due to the seperate address and data busses.  limiting
pins and timing to conform to a 68000 standard kind of defeats the purpose.
A huge cache would be nice, though, as well as faster divide and multiply
instructions.

>                  krooglik@gondwana4.ecr.mu.oz.OZ.AU

   -dave