I would say it's rather Qualcomm wasted the exclusivity deal so now others, given the chance, are trying to take a part of the pie for themselves, seeing Intel is at its weakest in years. Meaning if not for the rumored deal, we would probably see competition sooner in this space.Microsoft really proved "If you build it, they will come" with Windows on ARM.
The cost of having to build the SW ecosystem for RISC-V would likely outweigh the license/royalty costs. Better wait a few (10?) years that the RISC-V SW ecosystem matures.I could see AMD maaaybe trying something, if they were planning to start designing custom ARM cores anyway (for servers and maybe laptops), but considering the licencing models ARM is forcing right now, i think it would make much more sense to go the RISC-V way (if they indeed were planning to diversify their lineup).
That means they are not actively blocking it, not that they are contributing something to it. For instance DLSS 2 support was enabled by Nvidia offering the missing DLL file for use in Wine. I'll have to look what "support" entails in this case...Valve added DLSS 3 support to proton.
Latest Valve Proton Experimental update enables DLSS 3 Frame Generation and fixes performance in dozens of games
The November 12th Proton Experimental update implements and improves upon Proton 9.0-3www.tomshardware.com
That explains the DLSS side of things but Nvidia isn’t the one developing a ARM branch of Proton.That means they are not actively blocking it, not that they are contributing something to it. For instance DLSS 2 support was enabled by Nvidia offering the missing DLL file for use in Wine. I'll have to look what "support" entails in this case...
Found this: https://github.com/jp7677/dxvk-nvapi/pull/213
So it's another case of a Windows library file passing data to the Nvidia closed source driver doing the actual work, contributed by an Nvidia employee. So not exactly Valve's work, nor actually open source.
And Valve is most certainly not doing it for Nvidia.That explains the DLSS side of things but Nvidia isn’t the one developing a ARM branch of Proton.
That’s I why I said it’s likely for a future Steam Deck or steam hardware product that uses ARM. Most likely from AMDAnd Valve is most certainly not doing it for Nvidia.
valve is investing heavily into arm builds of proton
Where is this fabled ARM branch of Proton btw? I can't find it. All I found is a closed issue (https://github.com/ValveSoftware/Proton/issues/7553) as well as a test application (https://steamdb.info/app/3043620/history/?changeid=25321568).developing a ARM branch of Proton.
this is a good thread.Where is this fabled ARM branch of Proton btw? I can't find it. All I found is a closed issue (https://github.com/ValveSoftware/Proton/issues/7553) as well as a test application (https://steamdb.info/app/3043620/history/?changeid=25321568).
Thanks. Seems to me like Valve is continuously looking at ARM compatibility without a specific target so far. Started with SteamVR and could be for anything at this point. But as long as there's no public development I wouldn't hold my breath that there'll be a big reveal anytime soon.
Don't be surprised if it ends to be real knowing the current situation.Windows for RISC-V using Keller's Ascalon cores fabbed at Rapidus.
The Future
Are those stock arm cores?Latest MLID stuff.
As usual, his analysis is bad, such a part is pretty clearly a premium ULP part for Microsoft.
Van Gogh was that too, funny story.
Sonoma Point is the Mendocino replacement on Samsung 4nm.
View attachment 120426
Probably?Are those stock arm cores?
Sonoma *valley* right ?Sonoma Point is the Mendocino replacement on Samsung 4nm
2 A7xx cores and 4 A5xx cores? That would be a dream come true /sAre those stock arm cores?
Something with a 16MB MALL and 128-bit 9600 mem controller certainly isn't a Mendocini successor, I agree.Latest MLID stuff.
As usual, his analysis is bad, such a part is pretty clearly a premium ULP part for Microsoft.
Van Gogh was that too, funny story.
Sonoma Point is the Mendocino replacement on Samsung 4nm.
View attachment 120426
Right, forgot about the poor nomenclature.Sonoma *valley* right ?
That supposed to be the codename for Zen 6-based desktop processors (a successor to current Zen 5-based Granite Ridge).What is Olympic Ridge supposed to be?
It is built for Microsoft, but if OEMs are interested, then sure.Something with a 16MB MALL and 128-bit 9600 mem controller certainly isn't a Mendocini successor, I agree.
However it seems from his wording that it might not be a Microsoft exclusive SoC but rather offered for OEMs.
Thanks!That supposed to be the codename for Zen 6-based desktop processors (a successor to current Zen 5-based Granite Ridge).
Anyways, with MALL and stuff it seems to be a "premium custom" segment.
So not dissimilar to Van Gogh? Hopefully this time OEMs won't reject it due to fewer CPU performance.It is built for Microsoft, but if OEMs are interested, then sure.
If anything its AX SOC competitor.Its most likely a base Mx comp SKU. gotta dethrone the macbook air and Microsoft does want that
Maybe MSFT did the classic of screwing over AMD againHowever it seems from his wording that it might not be a Microsoft exclusive SoC but rather offered for OEMs.
Medusa DesktopWhat is Olympic Ridge supposed to be?