I hope this is true, AMD is too bad, it is just GloFlo lacking behind all the time. From Tech to yield.Speaking of Fottemberg and TSMC and GloFo tapeouts: http://semiaccurate.com/forums/showpost.php?p=276505&postcount=4162
I hope this is true, AMD is too bad, it is just GloFlo lacking behind all the time. From Tech to yield.Speaking of Fottemberg and TSMC and GloFo tapeouts: http://semiaccurate.com/forums/showpost.php?p=276505&postcount=4162
Zen+ maybe. But to be able to base this development on a safe decision regarding process, the GloFo negotiation might have been too late.Porting an extremely complex design such as Zeppelin to a completely different process, just for a single purpose makes very little sense no matter how you look at it. Not that I would complain if such swap would be made though.
Funny thing about the "on package bios", "which takes 30 minutes to reset".
I know as a fact that the bios on these systems is not located on chip, but on the motherboard as usual. It would be impossible to have the bios located inside the CPU, since different boards require different code depending on their configuration. The bios contains initialization code & firmwares for the external peripherals, such as storage, network, audio, etc controllers and in some cases programming parameters for the VRM controller. Not to mention that nowdays most of the ODMs have proprietary functions in their bioses (such as tuning features).
So unless AMD plans to pre-program the CPUs to work only in a specific board model, or alternatively the ODMs plan to bundle the CPUs with their boards... well, make your own conclusions.
Zeppelin uses a new AGESA core version, but the basic layout & functionality is still the same as on previous platforms. Most, if not all boards will be using Aptio V bios from AMI.
Zeppelin does have a tiny ROM "on die", however it doesn't store anything bios related and there certainly is no need ever to "reset" it.
Also the SMU stands for "System Management Unit", it is not the abbreviation for AMD's SMT implementation like the "source" claims it to be. SMU is the "master of the puppets" on recent GPU ASICs and APUs / SoCs since Trinity. You've seen me talking plenty about the SMU in the past.
At least for now the multithreading implementation goes by it's original abbreviation, SMT.
Funny thing about the "on package bios", "which takes 30 minutes to reset".
I know as a fact that the bios on these systems is not located on chip, but on the motherboard as usual. It would be impossible to have the bios located inside the CPU, since different boards require different code depending on their configuration. The bios contains initialization code & firmwares for the external peripherals, such as storage, network, audio, etc controllers and in some cases programming parameters for the VRM controller. Not to mention that nowdays most of the ODMs have proprietary functions in their bioses (such as tuning features).
So unless AMD plans to pre-program the CPUs to work only in a specific board model, or alternatively the ODMs plan to bundle the CPUs with their boards... well, make your own conclusions.
Zeppelin uses a new AGESA core version, but the basic layout & functionality is still the same as on previous platforms. Most, if not all boards will be using Aptio V bios from AMI.
Zeppelin does have a tiny ROM "on die", however it doesn't store anything bios related and there certainly is no need ever to "reset" it.
Also the SMU stands for "System Management Unit", it is not the abbreviation for AMD's SMT implementation like the "source" claims it to be. SMU is the "master of the puppets" on recent GPU ASICs and APUs / SoCs since Trinity. You've seen me talking plenty about the SMU in the past.
At least for now the multithreading implementation goes by it's original abbreviation, SMT.
This is a good indication. Some months ago I wrote that AMD isn't honest to us about their failed 2016 target, it seems even worse than I thought. This is what they called on track, they lied
If anything the payments amd made to glofo would be about allowing Zen to be fabbed at samsung based on demand. People are getting caught up in the wishfull thinking of Zen competing with quadcore *lake in absolute ST performance. If Zen delivers it will be server demand filling the Fab's.
AMD's 4 Zepplin SOC helps against one of intels best advantages , building high clocking low variance 500mm+ CPU's and the power/clock scaling in nowhere near the same issue for server parts thax to the low TDP per core.
Was not the deal about producing also on other foundries (TSMC)? I remember that the deal was about to break the exclusivity...
Well on top of all that we know Bristol ridge doesn't have this magical on chip BIOS scheme, yet both share the same platform.
I think so, too.If anything the payments amd made to glofo would be about allowing Zen to be fabbed at samsung based on demand. People are getting caught up in the wishfull thinking of Zen competing with quadcore *lake in absolute ST performance. If Zen delivers it will be server demand filling the Fab's.
I don't think Fott have meant that there will be one single SKU built on 16 nm FF+ processPorting an extremely complex design such as Zeppelin to a completely different process, just for a single purpose makes very little sense no matter how you look at it. Not that I would complain if such swap would be made though.
I don't think Fott have meant that there will be one single SKU built on 16 nm FF+ process.
For example, it would be wise to built the lower cost SKUs on GloFo process, and the higher margin ones on TSMC. And the APUs would benefit massively, especially when we consider that they are rumored to use Vega architecture and HBM memory chips. AMD invested some time and money in supply chain and interposer technology for TSMC process.
Is that SKU 8C/16T? Sisoft is displaying the 4 nodes as 64 threads which is odd if SMT is enabled and SKU is 16C/32T. Base clock is rather low 1.44Ghz, still decent performance.
The SKU can be right but the details still detected wrong, and cores can be disabled but still read as enabled.2S1451A4VIHE4_29/14_N is a 32C/64T SKU.
It would be overly optimistic to assume that Sandra can detect anything correctly on these chips. However the nominal clock frequencies of ES parts can be decoded directly from the SKU.
Being the one who spotted these first a few days ago, I had some more time to think about them.The SKU can be right but the details still detected wrong, and cores can be disabled but still read as enabled.
In the mem test, it is read as 8C but 64T.
Sent from HTC 10
(Opinions are own)
The scores are good or bad?
They seem to be held back by something, leading to very mixed results (just ckeck the ranking positions).The scores are good or bad?
We have no uarch + process + manufacturing data to model this.According to a calculation that I made a while ago (maybe Dresdenboy remember it, as we excanged it over twitter) a 2.4GHz core should draw below 5W, so a 180W 32c 2.4-2.5GHz base clock is feasible...
The ES have low clock for stability tests...