SI
SI
discoversearch

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 : Intel Corporation (INTC)
INTC 35.10+2.3%Nov 19 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: semiconeng who wrote (106318)7/29/2000 2:42:07 PM
From: Dan3  Read Replies (1) of 186894
 
Re: I guess that I have to explain this to you again. It is far wiser to bring up a new process on a product that is working well...

You continue to make my point for me. You appear to be claiming that, as late as next fall, Willamette will not yet be working well.

Next fall, Willamette will be a year old processor.

When the move was made from .25 to .18, Katmai was pretty much brand new, so Dixon - the most advanced processor Intel had more than two months experience with at that time was used for the production introduction. The other reason for using those .18 wafers for Dixon was that its on-die cache would have made it too large and power hungry for a mobile chip. It made sense to use those wafers for Dixon.

Now we've heard plenty about the larger die size and higher power consumption of Willamette. A year from now, unless it has a lot of unsolvable problems, it should be a perfect candidate for .13. But those wafers are going to be used for a Coppermine variation instead.

I think that somebody at Intel is very worried about some aspect of Willamette. I don't know if it's performance, scalability, compatibility, infrastructure support, or something else. But it is expected to still be a problem a year from now.

Dan
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext