Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re:  The 68050 - end of the 680x0? (was Re: The Amiga's Future)
Message-ID: <14198@pasteur.Berkeley.EDU>
Date: 20 Jun 91 18:22:09 GMT
References: <5171@orbit.cts.com> <75@ryptyde.UUCP>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 20

In article <75@ryptyde.UUCP> dant@ryptyde.UUCP (Daniel Tracy) writes:
>Are you kidding? You're saying something to the effect that, in the IIfx,
>a 50MHz 030 is used, but it is slowed down to 40MHz for some reason/somehow?
>Please explain this, this is very interesting.

I believe a sort of sleight ot hand was used.  40Mhz 68030s are actually
'failed' 50Mhz 68030's.  At least that's the story as I heard it.
Seems reasonable to assume that as Motorola's "success rate" goes up,
40Mhz become rarer, and you *might* start using 50Mhz parts....

And oh, by the way, memory allocation routines:

AllocAbs(), Allocate(), AllocEntry(), AllocMem(), AllocVec() [2.0],
AllocRemember(), etc.

Hmm, I guess we do have "Dynamic Memory Allocation".  Whatta you think? :)

David Navas                                   navas@cory.berkeley.edu
	2.0 :: "You can't have your cake and eat it too."
Also try c186br@holden, c260-ay@ara and c184-ap@torus