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 : All About Sun Microsystems

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: rudedog who wrote (27096)2/1/2000 11:48:00 AM
From: QwikSand  Read Replies (1) of 64865
 
Dog:

Now I'm really confused. If I'm understanding you, you're saying that OSV's and box makers have work to do to accommodate McKinley apart from perhaps just compiler work (which I assume in most cases is Intel's job anyway).

So if McKinley tapes out, and Merced and McKinley are around at roughly the same time, and Intel forces people to ship Merced for revenue to the extent possible, then is it not the case that suppliers are going to have to be juggling different versions of systems at the same time? That is, they're building and testing incompatible operating systems and motherboards and backplanes for two different versions of the same processor simultaneously? This sounds either like a real mess and a real burden on Intel's partners, or the Register article is wrong.

At this point, it's probably still early enough in the pipeline for Intel to just sh*tcan Merced (for volume purposes) and go with an accelerated McKinley. If they try to make their customers go through the whole product life cycle with both, build enterprise-ready machines of both sorts shipping at around the same time, etc., especially when one of them (Merced) is likely to be a disappointing low-volume boat-anchor, that sounds intolerably costly. I'd tell Mr. Barrett to expect some angry phone calls.

Is this what you're saying is going on? Or are you saying the Register article is wrong?

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