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: Tenchusatsu who wrote (56415)	4/26/1999 10:49:00 PM
From: Rob Young	Read Replies (1) \| Respond to of 1570560

I will tell you this, however. Much of Merced's performance was targeted toward a late 1999 release, before the Merced delay. So it doesn't surprise me when you say that Merced is no where near 21364. The thing is, when will the 21364 be released? And considering that the 21264 was itself delayed over a year, will the 21364 be released on-time? Well according to Shannon (Shannon Knows Compaq) the 21364 is a "done deal". Since they already had a 21264 core, the work (I suppose) went mainly into getting the on-chip Network and Memory controller correct (can you believe on-chip? Still hard to believe in some ways). The 21364 powerpoint slides said RTL was underway at the time of the presentation. I have no idea when it tapes out. It will require .18 and so shouldn't show up until some time next year. I am going to say MPR missed that one also. Wildfire can't shine until 21364, Bill wants the DataCenter ASAP. NT needs DataCenter hardware (not 8-CPU toys). I bet 21364 goes volume the same time Merced does. I have nothing to support that, yet. I have a hunch that 21364 will be a nice trump card. EV68 will volume ship shortly after the first of the year.. .18 micron. There really isn't much to slow down or hold up 21364 given it is (again) a debugged 21264 with some switches and a large cache (simplistic, but not nearly the grand challenge 21264 was). My guess? 21364 volume ships June 2000 (or thereabouts). Finally, "since 21264 was delayed a year, what about 21364?" That question was beaten about a while back in Usenet. The 21364 team plugged along in parallel while 21264 was getting worked out. I suppose there came a time when the 21264 was debugged and those changes migrated to the 21364 team. The 21364 release will appear to come fast on the heals of the 21264 .. but as you point out it isn't a grand achievement of the 21364 team as much as it was a long delay in finally getting 21264 debugged that 21364 will show up relatively shortly thereafter. EV68 low-end (yet high performance part) EV7 high-end workstation and server part. Purrfect together. Got the bandwidth nailed, don't I? I can't take credit for that however...