blackkstar :
We won't be able to make any concrete deductions on how bad GF screwed AMD with bulk and SOI.
We know one thing for sure. If AMD had selected SOI, they couldn't present Kaveri at APU13 and start shipping it now, because GF has failed to execute their 28nm SOI plans. Their Fab 8 is not ready for mass production and Samsung is coming in their help, taking the control of the R&D dept.
Assuming GF gets its problems solved for late 2014 it would be... too late (haha), because then Kaveri would be competing against Haswell successor (Broadwell) and Intel promises a much more powerful iGPU for Broadwell. Then AMD would cancel Kaveri and release Carrizo.
Luckily AMD selected bulk and can now start to ship Kaveri for official launch at January. Also AMD is now tappingout 20nm chips on bulk and 16nm on bulk FINFET.
blackkstar :
Yeah, the 7850k is not that far behind Trinity in clock speed, but look at what happened with Richland overclocking. I can nearly guarantee you that you won't be seeing a single 7850k breaking 5ghz on air. And Richlands that did that were common.
To be quiet honest I would be surprised if Kaveri broke mid 4ghz range for maximum overclocks. I have a feeling that AMD used the clock speed tweaks they used on Richland to salvage a bulk product. Meaning that whatever AMD did that let Richland break 5ghz while Trinity had no chance was applied to Kaveri to prevent Kaveri from having catastrophic clock speed. RCM comes to mind and I have a very good feeling if AMD didn't beta test what they did to get clock speeds up with Richland than we'd be looking at a 2ghz range Kaveri high end model.
As said before:
The CPU in Kaveri will be overclocked beyond 4.5 GHZ without problems. It will not break worldwide records either.
The former phrase is based in leaked docs. The late phrase means that I don't expect Kaveri to break the 8GHz mark. ;-)
blackkstar :
I also don't expect Kaveri to overclock well at all because of what AMD did with FX. Clearly it was a better choice to release PD with a 20% clockspeed improvement than to release SR FX on bulk. That alone should speak volumes of why there is no SR FX.
I'm assuming things kind of went like this
1. AMD starts talking about Steamroller on AM3+ using 28nm SOI
2. Glofo completely screws it up with delays, tells AMD they can get their big 28nm SOI chip in mid to late 2014.
3. AMD decided to either go bulk with SR FX or just not to it at all
4. They find out clockspeed and overclocking hit that comes with bulk wouldn't make the chip 10% faster
5. Release PD parts with 20%+ clockspeed bump (FX 9000 series)
Before I speculated with AMD taking one of two possible ways. The second was "abandon FX-4000 and use Warsaw-like dies for FX-6000/8000/9000 refresh".
Warsaw promises further reduction in power consumption compared to Opteron. I assume that are using fully enabled resonant clock mesh. Efficiency in the desktop is secondary, but reduction in power consumption could be used for increasing base/turbo clocks and the ability to overclock beyond 5GHz on air.
But the 2104 desktop roadmap shows that they are not doing that.
Then the big question is why is not AMD reusing the dies that are fabricating for Warsaw also for the FX line? Why the old FX-line is extended to 2014 without any refresh? Why the FX-4000 series continue being sold when the 4-core Opterons are abandoned and Warsaw is 12/16 core?
The more likely answer to all that is "lack of demand". We know that the FX line didn't sell well. Therefore, AMD must have an inventory of old products that they want to sell and, at the same time, there is no room for a refresh that 'nobody' would purchase. By nobody I mean less than 1% of total gamers or so.
We also have leaked docs. that said that the 9590 was the last FX chip.
My belief is that AMD is extending the FX line up to 2014 for replacing it with an ultra-high-end APU in 2015 (FM3 socket). Time will say.
blackkstar :
Take a look at S|A, Kaveri missed targets all over. It didn't miss targets because bulk is just as good as SOI.
The S|A article is overly pessimistic. Several of us (including myself) discussed it in S|A forums.