That was a chip designed for mobile... grossly underpowered and poorly optimized for a PC replacement....
So this will be Snapdragon 8CX Generation 3
They already failed with 1 and 2 while Apple didnt with M1 because its far easier when you control the whole stack
For this to work..
...
The 8CX Gen 3 is not design for mobile smartphones. There is a sizable shift here with Gen 3. Excerpt from a comparison table:
" ....
AnandTech | SD 835 | SD 850 | 8cx Gen 1 | 8cx Gen 2 | 8cx Gen 3 |
Node | 10LPE | 10LPP | N7 | N7 | 5nm |
Prime Cores | 4 x A73 2.60 GHz | 4 x A75 2.95 GHz | 4 x A76 2.84 GHz | 4 x A76 3.15 GHz | 4 x X1 3.00 GHz |
Efficiency Cores | 4 x A53 1.80 GHz | 4 x A55 1.80 GHz | 4 x A55 1.80 GHz | 4 x A55 1.80 GHz | 4 x A78 2.40 GHz |
GPU | Adreno 540 710 MHz | Adreno 630 710 MHz | Adreno 680 585 MHz | Adreno 690 660 MHz | Adreno 8cx Gen 3 |
Qualcomm’s 8cx Gen 3 for Notebooks, Nuvia Core in 2022/2023
Gen 3 using mobile "big" (or at best medium size) cores as the "little cores"/E-cores. And it uses the larger for mobile X1 cores in a quad cluster. Qualcomm's and Samsung's mobile headset offerings have. one X1 core and A55 based "little cores"
https://www.anandtech.com/show/16463/snapdragon-888-vs-exynos-2100-galaxy-s21-ultra
Google's Tensor uses two X1's but still is using A55's for "little cores"
The 8cx gen 3 is NOT going into any phone. There might be a larger Android Tablet with it. But there may be Windows slate Tablets too.
This will be an entirely new chip from the ground up.
Not really.
"...
IC: If you can perhaps clear something up for me: is the Nuvia team making a single core, or both a big core or a little core? Or is it that they’re dealing fully with the SoC structure into which you add in the connectivity and the graphics?
AK: It’s both, all the above. By that I mean that it's impossible for us to put out a chipset solution as sophisticated as this without having the entire system being taken into consideration. Think of it this way: the CPU by itself is part of the ‘one technology roadmap’, but so is graphics, and other things. Then we're really thinking about bringing a complete system solution to the PC and changing it in such a way that you don't go after the traditional designs. ..."
https://www.anandtech.com/show/1723...pdragon-microsoft-nuvia-and-discrete-graphics
The Nuvia cores are just one subcomponent of the die. The graphics , DSP/AI/ML cores , modem , Pluton , etc. are also components to the complete system die and will be evolutionary upgrades. More GPU cores but not necessarily a " blank, green field from ground up" GPU. Maybe some DirectX Ultimate additions but where useful on Vulkan and not a die space boat probably will see those upgrades flow though the other GPU implementations also. Same wtih DSP/AI/ML. Absolutely certainly with the modem part of the die (Windows isn't going to do much different there).
The Nuvia folks are not designing the whole chip. Qualcomm did not have to start from an empty slate to get this chip out in 2022-23. There is a more decent chance that due to the couplings between the GPU and DSP cores pefoirmance and the memory system that Qualcomm's folks are doing the memory subsystem also. All Nuvia's folks would be doing is plugging into the internal data/control bus(es) of the die. There is a very good chance Qualcomm already had (or even still has ) a team with more standard Arm X2 (or X3 depending upon timeline) designs that plug into the same internal bus .
Nuvia's cores are likely bigger so the overall die size budget probably needed to stretch but if the Nuvia acquisition didn't go through, it is extremely doubtful that Qualcomm had nothing in the hopper being developed to come out in 2023. The "tape in" of the different subsystems here is being juggled and adapted , but there likely was a foundation to build off of.
P.S. there is a pretty high likelihood that back pre-acquisition the Nuvia folks where not doing the whole server chip design either. Taking the baseline Neoverse design and just substituting in their own CPU cores would have made tons more sense with the limited time , budget, and manpower their had. Also makes them a more easier target to go an buyout of if their cores can plug into a more conventional Arm internal bus .
A system and power management , memory system , etc that already works with Linux would be a significant accelerator for adoption if most of the system die is the same.
Once they were started and had some revenue flow then taken on more internals. But if part of the objective was to get acquired ... tons of effort reinventing the wheel .. that is just a waste with little to no added value long term.
Last edited: