Google I/O: Qualcomm Celebrates Launch of Adreno 420 GPU for Android Gamingby Ryan Smith on June 23, 2014 1:00 PM EST
With Google’s annual I/O developers’ conference taking place this week, this should end up being a busy week for Android news. The conference itself doesn’t officially start until Wednesday the 25th this year, but several partners are already chomping at the bit to get going. First among these will be Qualcomm, who will be using the backdrop of the I/O conference to celebrate the launch of their latest high-performance SoC-class GPU, the Adreno 420.
Adreno 420 is the first member of Qualcomm’s next-generation SoC GPU family to make it out the door and in to a finished product, bringing with it OpenGL ES 3.1 and Direct3D 11 functionality. First announced last year as part of the Snapdragon 805 SoC, Snapdragon 805 and by extension Adreno 420 is now shipping in Samsung’s just-announced Galaxy S5 Broadband LTE-A. The S5B marks the first Adreno 420 product to reach consumer hands, and for as much as an SoC can have a formal launch this would be it, with Qualcomm celebrating its launch coinciding with this year’s Google I/O conference.
For Qualcomm the Adreno 420 in particular is an especially big deal since it is the first GPU to ship based on the Adreno 400 architecture. The Adreno 400 architecture marks a significant advancement in the feature set of Qualcomm’s GPUs, bringing Qualcomm’s latest architecture generally up to par with the existing desktop GPUs by integrating full Direct3D feature level 11_2 functionality alongside the more mobile-focused OpenGL ES 3.1 feature set. By doing so Qualcomm has reached feature parity with desktop GPUs (for the time being), even slightly exceeding NVIDIA’s GPUs by Direct3D standards due to being an FL 11_2 architecture versus NVIDIA’s FL 11_0 architecture.
As we have already covered Adreno 420 in some depth last month we won’t spend too much time going over it now, though admittedly this is also partially due to the fact that Qualcomm is remaining tight lipped about the Adreno 400 architecture beyond a high-level feature standpoint. In brief the Adreno 400 architecture (and Adreno 420) is a full Direct3D FL 11_2 implementation, utilizing a unified shader architecture along with the appropriate feature additions. New to the Adreno 400 architecture is support for tessellation, including the necessary hull and domain shader stages, and as a Direct3D 11 product this would also include with it other Direct3D 11 features such as compute shaders and draw indirect support.
Meanwhile on the OpenGL ES side of matters, while ES 3.1 is not as expansive as Direct3D 11, this none the less means that the Adreno 400 architecture brings with it ES 3.1 functionality along with a number of its Direct3D-derrived features as extensions. Mobile developers will also be happy to hear that this is the first Qualcomm product to support adaptive scalable texture compression (ASTC), the OpenGL next-generation compression technology that should further improve, unify, and simplify the use of compressed textures on mobile platforms.
For Google I/O we are expecting Qualcomm to be heavily promoting the Android gaming possibilities of the Adreno 420 and the Snapdragon 805. The low power nature of mobile devices and the SoCs that power them means that while Qualcomm can’t match the performance of the larger desktop GPUs, Adreno 420 will be a big step up from the performance offered by the older Adreno 330 GPU. But more importantly for Qualcomm, they can do something that hasn’t been done before by bringing desktop-level features to Android devices.
From our May 2014 Snapdragon 805 Preview
In a sense this will be a repeat of the launch of Direct3D 11 on the desktop, except now with Qualcomm (and eventually other vendors) promoting the advanced features offered by these devices, throwing out examples and tools at developers to entice them to write games for this latest generation of hardware, and to otherwise put it to good use. Even without being able to match desktop processors, there are a number of effects that are made available (or at least more practical) via these new features, and can be used effective on mobile hardware. From a practical perspective Qualcomm should be able to offer Android developers the base graphics functionality of the current generation consoles at performance levels similar to the previous generation consoles.
Post Your CommentPlease log in or sign up to comment.
View All Comments
tuxRoller - Wednesday, June 25, 2014 - linkThey aren't running at 1440 natively but some fraction there of, say 720 and scaled up.
The nice thing about high DPI screens is that you can have your cake and eat it to depending on what's important to you.
darkich - Wednesday, June 25, 2014 - link^ that was my very point.
tuxRoller - Friday, June 27, 2014 - linkErgh, yeah. I mistook your point😊
eddman - Tuesday, June 24, 2014 - linkA sort of off-topic question; did AT ever write about the Mali-T7xx series of GPUs?
Wonder how adreno 4xx will fare against them.
Mali-T760 seems to be the GPU that will give K1 a hard time.
Any thoughts on that?
Ryan Smith - Tuesday, June 24, 2014 - linkAlthough we're not in a position to talk about performance, we'll be talking about Mali's architecture very soon.
przemo_li - Tuesday, June 24, 2014 - link+1
And folks. Switch to OpenGL versions. (Aspecially since one can get very good per-extension expanations of what new stuff in given OGL do)
DX FL ... Even Nvidia do not cares about them that much ;)
darkich - Tuesday, June 24, 2014 - linkAccording to Antutu 3D test, Mali T760 clearly outperforms the Adreno 420
Another advantage of Mali 760 is the scalability, so the MP16 variant could in theory outperform even the K1 GPU
tuxRoller - Tuesday, June 24, 2014 - linkAccording to antutu, the tegra 4 outperforms the snapdragon 801, iirc.
darkich - Wednesday, June 25, 2014 - linkAntutu 3D test runs at native resolution so it is no wonder that Tegra 4 at 720p indeed performs better than Snapdragon 801 at 1080p.
daku123 - Wednesday, June 25, 2014 - linknvidia doesn't much care about MP16 since Tegra 4 and onwards. That is why they perform poor as compared to Imagination Tech's/Adreno counterpart on some android benchmarks. They mostly want their GPU cores to be more flexible (in other words they want it to work on all sort of devices including AIOs and Cars; and desktop GPUs of course). I am pretty sure that 32 bit operations are much faster on Tegra K1 than any other existing/next one year mobile SOC.