News Focus
News Focus
icon url

wbmw

02/10/14 11:21 AM

#129497 RE: This Causes an Error #129494

Ever wonder why Intel jumped straight to Westmere for the mainstream dual core parts with no dual core Nehalem ever showing up?


My guess is that the 45nm parts were delayed, and they shifted priorities to 32nm shrinks of those designs.

You do realize that Intel has never been a perfectly executing business. It just didn't matter in the past, because they always had a weak competitor, and an abundant enough investment in the PC business that they always had a fallback.

The difference now is that they underinvested in mobile, course corrected several times to find it still wasn't enough, and now their next leadership product is (at the earliest) about 5 years late. I know it sucks, but as far as Merrifield goes, that horse is dead, and yet you keep beating it mercilessly.
icon url

simplytom

02/10/14 12:24 PM

#129512 RE: This Causes an Error #129494

@aeassa



Mas, these are very interesting details. I'm particularly interested in the fact that Haswell has in fact FIVE unique die implementations, built from scalable IP. Haswell is a big jump for them into more of an SOC methodology.


Agree. They've come a long way from what happened with the development of Nehalem. Ever wonder why Intel jumped straight to Westmere for the mainstream dual core parts with no dual core Nehalem ever showing up?



Because Core 2 Duo was so strong. It had a much more simpler approach (no L3-Cache) and was still very very fast.
icon url

DavidA2

02/10/14 2:49 PM

#129524 RE: This Causes an Error #129494

Yea. Havendale and Auburndale were seriously delayed so they pulled in Clarkdale.