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.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: Petz who wrote (18360)	11/9/2000 1:55:53 PM
From: andreas_wonisch	Read Replies (2) \| Respond to of 275872

Petz, Re: The thing that died is the large cache version of Palomino, apparently. That's what I am saying. It was called Mustang before, I never heard of "Palomino with large 2nd level cache for servers". Andreas

To: Petz who wrote (18360)	11/9/2000 1:57:41 PM
From: aburner	Respond to of 275872

Petz, re: Mustang = generic name for Palomino, Morgan Thanks for clarifying. So do you think we'll get some information on Palomino next week at Comdex? ABurner

To: Petz who wrote (18360)	11/9/2000 2:07:11 PM
From: rsi_boy	Read Replies (3) \| Respond to of 275872

Large cache Mustangs, this was supposed to be the main improvement. On the bright side I guess this means they were sandbagging about performance (other architectural improvements than just cache "flexibility" -- as though tbird wasn't cache flexible already with 64k and 256k variants). I too hoped that AMD would be pushing for a premium branding niche. I don't understand the strategy of dominating the midrange when you don't have the capacity to achieve a majority share. Here's my theory to explain all this. Large cache Mustangs sure would have helped ASP, but it seems everything hinges on SMP. The large cache is really only necessary in SMP/server situations in order to ease memory contention. Same goes for high-end/workstation positioning, it's hard to take AMD seriously on a purely uniprocessor platform. But with 760mp pushback to late Q2, that leaves only a six-month platform window before launch of k8. Hence AMD's dilemma and why server CPUs seem to be temporarily deemphasized on the road map. How the market will interpret this CC, it's hard to say. Market swamped by macro effects these days. My worst fear is that analysts will simply ignore AMD's fundamentals and guidance (eg status quo for the last six months) t. [edited]

To: Petz who wrote (18360)	11/9/2000 2:09:47 PM
From: andreas_wonisch	Read Replies (1) \| Respond to of 275872

Petz, concerning the Mustang name confusion: Yeah, let me start with Mustang, Corvette, and Camaro, which are the three enhanced versions of our current seventh generation products, which are scheduled to be introduced here in the fourth quarter this year. We're still on track for that. Mustang, of course, being the high-end server and workstation part, along with our IGD42P chipset, providing our first opportunity to really penetrate the server space and garner some entry into the enterprise market - again, expanding the opportunity to really sell product. This is from the Q2 CC. After that Camaro was changed to Morgan and Corvette to Palomino due to copyright issues with GM. The name Mustang for the whole family was conceived later. Mustang was always the server CPU with large 2nd level cache. Andreas