Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?

To: Jim McMannis who wrote (75812)	10/18/1999 1:02:00 AM
From: Tenchusatsu	Respond to of 1571741

<They did go from 333 on .35 to 600 on .25u though didn't they?> Jim, Pentium II 333 MHz was a Deschutes, not a Klamath. Intel's 0.35u process never did go over 333 MHz. In other words, Intel went from 300 to 600 MHz with one process generation (and a slightly revised core), doubling the frequency. If the next process generation led to another doubling of the frequency, then Coppermine will eventually reach the 1.2 GHz that Process Boy is tossing around. Yeah, I know, it's inconceivable for a mere "sixth-generation" core to reach any speed over a gigahertz, isn't it? Tenchusatsu

To: Jim McMannis who wrote (75812)	10/18/1999 1:03:00 AM
From: Charles R	Read Replies (3) \| Respond to of 1571741

<From 600 MHZ on .25 to 1.2 GHZ on .18u would be exceptional. I would be very surprised.... They did go from 333 on .35 to 600 on .25u though didn't they? > A few things to consider: On the positive side - CuMine uses extra layer of metal for local interconnect and layout guys seem to have taken care of some of the critical RC paths to help the ramp. On the negative side - 0.35 was not pushed as hard and did not get the benefit of the jacked-up voltage. I am very much fascinated by the battle so far. Intel appears to be losing so far but has definitely put in a phenomenal fight and is not conceding anything easily. I guess Intel is looking for an "unforced error" from AMD which hasn't come so far (at least on the process side).