Arm Mali G2-Ultra NX GPU: desktop-class mobile gameplay with AI-native graphics
Posted by Re-Tails 10 hours ago
Comments
Comment by ksec 9 hours ago
I wonder how far or how good Mali is now compared to others. I wish Chip and Cheese do compassion on GPU as well.
Comment by pjmlp 7 hours ago
Unless it is a Pixel or Samsung Sxy flagship device, chances are the driver, which will never get updated, it a box full of interesting developer moments.
Just go to chrome://gpu to check the amount of workarounds enabled in Chrome alone.
Comment by MindSpunk 1 hour ago
It's depressing how bad the drivers are. They have 0 market pressure to improve the quality, unlike PC where the whiniest group on the internet (gamers on reddit) will crucify you for driver problems. I've spent too much time investigating and implementing workarounds. Though it does pay my bills...
Comment by catchnear4321 2 hours ago
thank you, will be using this, it’s far more accurate than simply throwing the devs under the bus and ignoring all the unspoken context of said moments, while not papering over the… interesting developer moments.
Comment by nubinetwork 2 hours ago
Comment by dbcooper 3 hours ago
Comment by Alpha3031 15 minutes ago
Comment by teki_one 9 hours ago
Comment by throwa356262 8 hours ago
Example benchmark showing how extremely far Google is behind:
GeekBench 6 Compute Score (GPU):
Xring O3. 36901. (the GPU in this announcement)
Snapdragon 8 Elite G5 27501. (Adreno 840)
Dimensity 9500M. 23753. (Mali-G1 Ultra MP11).
Tensor G6. 6216. (PowerVR CXTP-48-1536)Comment by MindSpunk 7 hours ago
And then Google has the gall to charge basically flagship prices for their under powered junk.
Personally I don't buy flagship phones because I don't use their full compute capabilities anyway, but a Pixel 11 would cost 2x what I paid for my Pixel 8. For 0 GPU performance improvement.
Comment by Fr0styMatt88 2 hours ago
Comment by ahknight 40 minutes ago
Then Samsung got the message, ran with it, and Google went "Ehh, we're good now."
Comment by ksec 7 hours ago
I just can't wait to see it being tested in an actual phone. So far all the data are done on development board. If they are really as good as everything we have read so far, both Mediatek and Qualcomm are in big trouble.
Comment by my123 5 hours ago
Comment by throwa356262 6 hours ago
Comment by rjzzleep 4 hours ago
Comment by eptcyka 9 hours ago
Comment by bigbaguette 9 hours ago
Comment by eptcyka 9 hours ago
Comment by david-gpu 4 hours ago
First, they would spill all of their secret sauce for others to "draw inspiration" from. And there is a lot of expensive secret sauce in there. Not all of it is protected by parents either; more on that below.
Second, they would make it a lot easier for competitors and patent trolls alike to seek litigation. One of the criteria thech companies have for filing a patent is how easy is it to detect when it is being violated. Open source your stuff, and you make it much easier for the competition to detect any violation.
And it is not like these companies are violating patents intentionally; much the opposite. But there are only so many ways to implement Vulkan or DirectX, and completely independent teams will come up with similar enough solutions, and with broad enough patents, that there will be overlap every now and then. That is why they file patents in the first place. Only the high cost of litigation and the risk of mutually-assured destruction keeps legitimate vendors from rattling sabers more often.
Then you have NVidia with their immense investment and advantage on the software side, from the CUDA runtime to countless libraries like CUBLAS and cuDNN. That investment goes much beyond a relatively simple Vulkan/DirectX driver.
So the question is less "why don't more of them open-source userland". The question is "why do any of them do it"?
Source: former insider with enough patents under my belt that I lost count.
Comment by amelius 44 minutes ago
> First, they would spill all of their secret sauce for others to "draw inspiration" from. And there is a lot of expensive secret sauce in there. Not all of it is protected by patents either
Then why does Apple allow Asahi to reverse-engineer their low-level APIs? Are their lawyers not paying attention?
Comment by eptcyka 1 hour ago
Comment by david-gpu 1 hour ago
Just speculating here. Maybe they have big customers that communicated to them that they will choose them over the competition if they open more of their software stack. Maybe they are less afraid of being sued because they are the underdog and they believe that the authorities would not be kind to a behemoth suing them, or they believe that the behemoth would not sue them because of the bad press it would generate vs the settlement they would get.
I actually don't know. But I am sure they have good reasons, just like the corps that keep it closed also have good reasons. It is not "good" vs "evil".
Comment by eptcyka 31 minutes ago
Comment by pjmlp 6 hours ago
Any conference talk schedule at one of these conferences (https://gameconfguide.com) will prove the point of how little they care.
It is all about gameplay, taking advantage of gaming IP, franchaises, how to squeeze the ultimate performance out of specific hardware, user engagement,....
You will find an occasional talk about open APIs, probably even done by some Khronos folks, and that's it.
Comment by krautsauer 9 hours ago
> Moats were excavated around castles and other fortifications as part of the defensive system as an obstacle immediately outside the walls.
Unfortunate wording?
Comment by dbdr 9 hours ago
Comment by buran77 5 hours ago
Comment by ImHereToVote 7 hours ago
Comment by throwa356262 8 hours ago
I thought these GPU were open source with mainline kernel support?
Comment by adrian_b 4 hours ago
Thus there is a considerable lag for the support of newer Mali generations.
Some Linux distributions for various embedded computers with Arm-based CPUs and GPUs use closed-source GPU drivers from Arm, not the reverse-engineered Linux drivers, when the Mali versions are newer than supported by the kernel and Mesa.
The Arm GPUs do not have public technical documentation, not even at the level of NVIDIA, much less something comparable with AMD and Intel.
Comment by throwa356262 3 hours ago
Mali drivers are contributed by Arm:
Comment by adrian_b 3 hours ago
Besides the Mali generations that are supported in the mainline kernel, there are many other Mali generations for which Arm has not provided anything else except closed-source drivers for Android, in a few cases also closed-source drivers for Linux. However, there are many other reverse-engineered Mali drivers, besides those from the mainline kernel.
It is good that Arm has begun to contribute to the kernel DRM drivers, but these drivers do little else except providing the means to communicate with the GPUs. The complex work is done in the user-space GPU drivers from Mesa.
The Mesa Lima driver, for older generations of Mali, does not have any contribution from Arm.
In the past, Mesa Panfrost was also completely reverse-engineered. Seeing that now Arm has begun to contribute to the kernel Panfrost DRM, I do not know whether they have started to contribute also to the Mesa Panfrost.
In any case, while some contributions to the previously reverse-engineered drivers are much better than nothing, what would have been much better is to publish the technical documentation of the Mali GPUs, in which case it would not have mattered whether Arm contributes something or not, as anyone could have written the drivers.
Comment by fuzzfactor 4 hours ago
Comment by ginko 4 hours ago
That's not true. Arm has been supporting the open source driver effort for the last couple years, but it's still behind the closed source one in terms of performance, features, and HW support.
Comment by touisteur 3 hours ago
Comment by pavlov 3 hours ago
I guess that's nice and makes sense on mobile, but it somehow feels a bit disappointing that realtime 3D is shifting from modeling to slop filters.
Comment by mepian 2 hours ago
Comment by zamadatix 28 minutes ago
Comment by cubefox 3 hours ago
This is another story with DLSS 5, which doesn't reconstruct some ground truth and which is a pure post-processing effect. It just makes the final image look more photo-like in a vague sense. This is more of a "slop filter".
Comment by curiobleak 7 hours ago
Comment by swiftcoder 28 minutes ago
Comment by HNSheldonImpost 49 minutes ago
Comment by mschuster91 3 hours ago
Comment by jlg23 2 hours ago
* Neural Super Sampling (NSS) reconstructs higher-resolution images from lower-resolution renders, reducing the amount of conventional rendering work needed to produce a high-quality final image.
* Neural Frame Rate Upscaling (NFRU) generates intermediate frames to increase frame rates and deliver smoother gameplay.
* Neural Super Sampling and Denoising (NSSD) combines neural upscaling with denoising to improve image quality in demanding ray-traced scenes with complex lighting and shadows.
Comment by mschuster91 1 hour ago
Comment by chrisjj 43 minutes ago
And nor is reconstructs true.
Comment by BoingBoomTschak 2 hours ago
https://www.semiaccurate.com/2026/09/07/arms-2026-tech-day-i...
https://chipsandcheese.com/p/arms-c2-ultra-g2-ultra-nx-and-c...
Comment by cubefox 8 hours ago
Comment by alescalaios 4 hours ago
Comment by gitowiec 6 hours ago
Comment by chromehearts 6 hours ago
Comment by mobelkh 2 hours ago
Comment by f6v 5 hours ago
Comment by mrheosuper 6 hours ago