Cazalan :
There is no way that Jaguar can scale up to 4 GHz. This is a low frequency design that tops on about 2 GHz (probably the optimal freq. is about 1.5--1.6). AMD is taking here a wise approach with two (three if you count ARM) architectures optimized to different markets.
The core design/architecture doesn't fully dictate it's speed. The transistor layout/optimization and process technology have a bigger hand in that. The same design can be tuned for low power or high performance with different standard cell libraries. Intel does it all the time between their UltraLow voltage, mobile and desktop versions of chips.
The A6-5200 is their top Jaguar chip which is standard at 2.0Ghz. I doubt they would ship product at maximum rated clock if that was the true limit. It may be near the limit on the TSMC process today but Sony registered the PS4 with 2.75Ghz max clock speed.
The 2Ghz limit is likely to just meet their desired target of 25W. I expect they will release new SKUs to keep up with Intel Silvermont when they launch. Jaguar supports turbo modes so they could add a 2.0/2.4 version with say 30W TDP.
If you look in the Kabini guide the registers actually support up to 6.3Ghz.
http://support.amd.com/us/Processor_TechDocs/48751_BKDG_Fam_16h_Mod_00h-0Fh.pdf
MSRC001_0071 COFVID Status
[54:49] MaxCpuCof: maximum core COF. Specifies the maximum CPU
COF supported by the processor. The maximum frequency is 100 MHz * MaxCpuCof.
With a 6 bit field that's 0x3F or 63x100Mhz = 6.3Ghz
Maybe they just threw an extra bit in there for future proofing but even with a 5 bit field they would have a 3.1Ghz cap. They must have envisioned it going past 3.1Ghz in the not so distant future.
I didn't say that 2GHz is a limit, but that is the top frequency used by AMD. Probably jaguar can be clocked at 2.6GHz, the same that you can OC Richland up to at 5GHz on air. But 2GHz is the frequency chose by AMD for jaguar in base to its own safety and power consumption requirements.
Cazalan :
juanrga :
Wrong again. The above GFLOP are the numbers claimed by Intel for the CPU. The 448 GFLOP of haswell i7 CPU are reported in several sites.
Intel likes to use DP in its technical datasheets. If you want to obtain DP values you only need to divide the above SP numbers per 2. E.g. the 224 GFLOP (SP) correspond to 112 GFLOP (DP).
Intel posts their GFLOPs here for export regulations:
http://www.intel.com/support/processors/sb/CS-017346.htm
i7-3770K
Base (3.5)
112
Turbo (3.9) 125
GPU Only 147.2
Exactly as I said. 112 GFLOP (DP) for the i7-3770k. For SP the number is the double: 224 GFLOP.
i7-3770k: 4C x ( 16SP FLOP per cycle ) x 3.5 GHz =
224 GFLOP
i7-3770k: 4C x ( 8DP FLOP per cycle ) x 3.5 GHz = 112 GFLOP
i7-4770k: 4C x ( 32SP FLOP per cycle ) x 3.5 GHz =
448 GFLOP
i7-4770k: 4C x ( 16DP FLOP per cycle ) x 3.5 GHz = 224 GFLOP
Piledriver: 4C x ( 8SP FLOP per cycle ) x 4.0 GHz =
128 GFLOP
Piledriver: 4C x ( 4DP FLOP per cycle ) x 4.0 GHz = 64 GFLOP
Steamroller: 4C x ( 8SP FLOP per cycle ) x 4.0 GHz =
128 GFLOP
Steamroller: 4C x ( 4DP FLOP per cycle ) x 4.0 GHz = 64 GFLOP
Total performance (CPU+GPU). I gave only SP performance and rounded:
i7-3770k: 224 + 294 GFLOP =
518 GFLOP
Richland A10: 131 + 668 GFLOP =
799 GFLOP
i7-4770k: 448 + 400 GFLOP =
848 GFLOP
Kaveri A10: 128 + 922 GFLOP =
1050 GFLOP
Cazalan :
juanrga :
Therefore, my suspicion that you don't have any link or source contradicting what AMD said about kaveri being bulk confirms. What you have is your interpretation of an interview to an executive of STMicroelectronics talking about Glofo!!!!!
It's true that AMD hasn't updated that statement, however it was made back in early 2012. At the time the roadmap also showed Kaveri being available the entirety of 2013, and there was no mention of Richland at all. The new roadmap in 2013 put Kaveri in the back 3rd of the year, and a Richland appeared to fill the gap.
In their recent conference calls they have outright refused to answer which chips are being made at GF. There is also speculation that Kaveri is now on it's 2nd generation as the first one tested too slow (The one that could have showed up instead of Richland). That first Kaveri may have been on a bulk process matching the CTO statement at the time.
With neither TSMC or GF shipping bulk chips past 3Ghz we can only HOPE that Kaveri is not on a bulk process. Boost "IPC" by 35% and cut frequency by 33%. You'd end up with the same performance (at best) although at a lower TDP. The same people saying Hasfail would have to say Steamfail as well.
Besides this is a Speculation thread. If we had to stick to official AMD statements there would be nothing past page 2.
It is entirely possible that AMD has changed its plans and I have no problem with speculation, but problem when people does not differentiate between personal speculation and official claims.
No problem with people believing that Kaveri is SOI, but problem when people says Kaveri
is SOI as if it was an official claim.
No problem with people believing that AMD will release FX Steamroller, but problem when people says AMD confirmed that will release FX Steamroller.
No problem with people believing on a 8 core APU, but problem when people says AMD will release a 8-core APU.
No problem with people believing that Steamroller has an improved FPU, or a doubled FPU, or two 256-bit FMAC units..., but problem when people says Steamroller
has that, whereas ignoring that AMD has confirmed, during Kaveri presentation, that Steamroller
has a 8 FLOP per cycle FPU like Piledriver.
And so on.
Now about your comments. The information that I have is that kaveri is going bulk on Glofo. AMD claimed that kaveri is bulk. The Japanese article cited by 8350rocks is from July this year and affirms that kaveri is being made at Glofo on a 28nm
bulk high-performance process.
Glofo claims that they can go beyond the 3 GHz on bulk.
You seem to claim that Kaveri one year delay is because they are moving from bulk to SOI. AMD vicepresident Roy Taylor has officially said, a pair of weeks ago, that the delay of kaveri is not due to architecture or process but due to
HSA. I interpret that AMD has delayed kaveri waiting more HSA enabled software available at launch.