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.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Bill Jackson who wrote (86076)1/9/2000 4:37:00 PM
From: Saturn V  Read Replies (2) of 1571936
 
Ref- <Do you think it is the baggage that goes with the 'notched' gates that is causing the yield problems>

The disappointing Coppermine availability has led to all kinds of speculation regarding Coppermine process yield problems.

My inferences:

The Coppermine design problem ( slow speed) surfaced last June. To improve speeds Intel quickly attached a new process module with notched gates and faster transistors to the existing 0.18 micron process.

Unfortunately with no significant manufacturing experience on the new process ,[ the earlier 0.18 micron process was running on a pilot line for more than 9 months+], Intel took the prudent approach of ramping the process slowly and starting only a limited number of wafers [ < 10%] on the new process. Apparently Intel has delivered 3million+ Coppermines, which indicates reasonably equivalent yields to the earlier products.

Shortly a design change will be in manufacturing, which will enhance speeds significantly. So in Q1 there should be more and faster Coppermines. Overall not the normal execution expected from Intel, but given the situation, it was pretty good.

AMD manufacturing is not as conservative as Intel. With the backs to the wall, they have taken major gambles which did not execute smoothly and caused the financial disasters of 98 and H1 99. However in H2 99 , the gambles have paid off.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext