Bondrewd
Veteran
But there's no CNL-H, only Y and U.Cannon Lake H will come next year.
As for CFL-H, I am not sure.
Probably no.
But there's no CNL-H, only Y and U.Cannon Lake H will come next year.
I find the relationship realy intresting. What is Intel doing when AMDs own APUs are stronger than Intel ones? AMD for sure knows now what APU Intel will bring! Intel is not knowing what AMD will throw into the APU market.
There's no CNL-H and we know nothing of CFL-H.Isn't CFL-H actually CNL-H? https://www.intel.com/content/www/u...ocessors-and-chipsets/platform-codenames.html
This may be the case, although the x86 group's future seems rather secure given the markets the Zen core is gaining share in.
If this deal is mostly about the monetary upside, and AMD's position in terms of integration technology and manufacturing isn't given a leg up by Intel's input, then this might be treated as a chance at getting cash that AMD wouldn't be able to get at anyway.
The encapsulation of the product makes it behave like a discrete GPU, albeit a more involved version of the Apple-centric Tonga discrete--particularly if Apple is one of the drivers for this.
AMD's logistics and integration tech seem like they aren't up to the task for a non-custom APU at this level of complexity and cost.
If AMD's integration/manufacturing doesn't improve, then at some point the x86 group could just assume that it will not be a factor in this particular space--and AMD overall is going to get what income it can.
Some of the articles say that this is an Intel CPU+IGP paired with GCN+HBM.Not sure one should be comfortable to accept the loss of a good margin sector and replacing that with a lower margin GPU deal that importantly also solidifies Intel CPU division for mobile and possibly some other segments and feel OK as Zen core is gaining share elsewhere.
The CPU division is where the best revenue and margins exist, AMD needs to expand that business as much as possible.
Apple or somebody else that feels like handling the complexity specific to a hybrid setup and disparate D3D12 feature levels/doesn't care about DX12. It does feel like someone is motivated enough to go through with this specific combination.If this deal only affects Apple well the fallout may be less but the announcement on the AMD side came from the Radeon gaming division VP Scott Herkelman, specifically he mentions AAA games and gamers, content creators, expanded set of enthusiasts.
The notable GPU to CPU relationship that isn't clearly covered by something like a Raven Ridge system with Vega 11 is the announced shared power management. If Vega 11 has HBM, and either Ryzen or Raven Ridge save area with their on-die southbridge, a substantial portion of the marketing features like area savings are shared.This is a great market to develop a complete CPU-GPU solution that is solely AMD, the margins in such segments are great.
Semi-custom at least early on was characterized as needing some hundreds of millions to a billion dollars in expected revenue at a minimum before AMD would bother. I'm curious if that still holds.I guess we will know more in the months to follow the scale of any such deals between Intel and the Radeon division and whether it has any meaningful impact on AMD business.
Some of the articles say that this is an Intel CPU+IGP paired with GCN+HBM.
I would have expected that the Raven Ridge designers had more lead time than Intel, but current information doesn't include the capability. Given the touting of AMD's new modular infrastructure, this should have been even easier to implement. I'd interpret this as the option being actively decided against.
RTG may supply the GPUs, but I wouldn't think it would have veto power over a more extensible Raven Ridge if the designers wanted it.
If there was a willingness to implement the fabric in Vega already, it seems like the next incremental step would have been to add PHY for it, although we don't know if plans changed with Vega 10/Greenland or what's going on with Vega 11.
Apple or somebody else that feels like handling the complexity specific to a hybrid setup and disparate D3D12 feature levels/doesn't care about DX12. It does feel like someone is motivated enough to go through with this specific combination.
The notable GPU to CPU relationship that isn't clearly covered by something like a Raven Ridge system with Vega 11 is the announced shared power management. If Vega 11 has HBM, and either Ryzen or Raven Ridge save area with their on-die southbridge, a substantial portion of the marketing features like area savings are shared.
It strikes me as counterproductive if RTG were allowed to circumvent AMD's overall product interests without the rest of the company being able to weigh in, but I have no visibility on any internal shenanigans.
Semi-custom at least early on was characterized as needing some hundreds of millions to a billion dollars in expected revenue at a minimum before AMD would bother. I'm curious if that still holds.
It's twice to thrice as hilarious considering BK's background.1) Completly mishandled process management and...
2) Lost the critical manufacturing leadership
Let's not forget them openly FUDing at AMDs multi-die approach while promising to deliver exactly it for 10nm products.5) Tharashed and flailed, marketing-wise in response to Ryzen/Thredripper like a drunk teenager caught urinating in a public park
Honestly retarded acquisitions happened even back in the Otellini days (member McAfee?).But hey, while the core market was a smoldering dumpsterfire, spent $18 billion dollars on a fledgling self-driving company in the process of losing its highest-profile client. Truly the best use of resources given the circumstances!
From my link:There's no CNL-H and we know nothing of CFL-H.
For now I'll assume it uses KBL-H.
Coffee Lake H 2-in-1, Notebook Released
Coffee Lake H Embedded Platform Code Named Coffee Lake – H with Cannon Lake PCH-H
That's PCH, duh.From my link:
Regarding business impact, I should say it can be both positive and negative.But it's more than just a little awkward that Chipzilla effectively threw its minnow of a rival under a truck, and has now picked its competitor up, dusted it off, slipped it twenty bucks for some GPUs Intel can't design itself, and told its tattered new best pal to smile for the cameras.
With friends like that, who needs enemies like Nvidia? ®
Goddammit, this is a semi-custom chip, RTG only did the design.Intel are not friendly at all to AMD and their CPU Division, yet we have this alternative situation with the Radeon group.
They don't need to, GPU users will be begging for EPYC themselves anyway.Anyway, to give a comparison on the Radeon deal, the CPU division might as well work with Nvidia to compete against a very dominant Intel (CPU perspective) in the HPC-AI/scientific/analytics
Interposers are not as cheap as EMIB; besides AMD most definetly has no time to serve such niche markets.Why didn't AMD simply do a Raven Ridge APU with scaled up GPU + HBM2?
Absolutely.The only thing that would make sense is that Apple ordered this chip for the next Macbooks.
Actually it's a threat to Intel only. Intel asked for semi-custom design.Apple moving Macbooks to their custom GPUs and CPUs is a threat to both Intel and AMD. This is the only sane reason why these companies would collaborate.
Interposers are not as cheap as EMIB;
Yet not fully connected, 2 hop diameter inside the package (well, at least to my understading).Imagine an Epyc style processor with EMIB inter-die links; much more bandwidth at lower power consumption.
The client side has seen success with Ryzen, the GPU group is whatever from the x86 standpoint, and non-console APUs just don't seem to be garnering much affection.
If AMD's proposed plans are to be believed, the monolithic APUs are going the way of the dodo anyway.