The GeForce ULV GPU

Tegra 2 integrates the GeForce ULV, an NVIDIA designed OpenGL ES 2.0 GPU.

At a high level NVIDIA is calling the GeForce ULV an 8-core GPU, however its not a unified shader GPU. Each core is an ALU but half of them are used for vertex shaders and the other half are for pixel shaders. You can expect the GeForce ULV line to take a similar evolutionary path to desktop GeForce in the future.

The four vertex shader cores/ALUs can do a total of 4 MADDs per clock, the same is true for the four pixel shader ALUs (4 MADDs per clock).

For those of you who follow NVIDIA’s desktop architecture: at the front end the machine works on a 4-thread warp, where each thread is a single pixel. 

Architecturally, the GeForce ULV borrows several technologies that only recently debuted on desktop GPUs. GeForce ULV has a pixel cache, a feature that wasn’t introduced in GeForce on the desktop until Fermi. This is purely an efficiency play as saving any trips to main memory reduces power consumption considerably (firing up external interfaces always burns watts quicker than having data on die).

 

NVIDIA also moved the register files closer to the math units, again in the pursuit of low power consumption. GeForce ULV is also extremely clock gated although it’s not something we’re able to quantify.

NVIDIA did reduce the number of pipeline stages compared to its desktop GPUs by a factor of 2.5 to keep power consumption down. 

The GeForce ULV supports Early Z culling, a feature first introduced on the desktop with G80. While G80 could throw away around 64 pixels per clock, early Z on GeForce ULV can throw away 4 pixels per clock. 

 

The ROPs are integrated into the pixel shader, making what NVIDIA calls a programmable blend unit. GeForce ULV uses the same ALUs for ROPs as it does for pixel shaders. This hardware reuse saves die size although it adds control complexity to the design. The hardware can perform one texture fetch and one ROP operation per clock.

While GeForce ULV supports texture compression, it doesn’t support frame buffer compression. 

Both AA and AF are supported by GeForce ULV. NVIDIA supports 5X coverage sample AA (same CSAA as we have on the desktop) and up to 16X anisotropic filtering.

 

We’ve done a little bit of performance testing of Tegra 2’s GPU vs. the PowerVR SGX 530/540 and Qualcomm’s Adreno 200/205. It’s too soon for us to publish Tegra 2 smartphone performance numbers, but the numbers NVIDIA is sharing with us show a huge advantage over competitive GPUs. In our own experience we’ve found that Tegra 2’s GPU is a bit faster than the PowerVR SGX 540, but nothing lines up with the numbers NVIDIA has shown us thus far. We’re still a couple of months away from final software and driver builds so it’s possible that things will change. 

The CPU: Dual-Core ARM Cortex A9 Memory Controller, Video Decode, HW Flash and Camera Processor
POST A COMMENT

21 Comments

View All Comments

  • DigitalFreak - Wednesday, January 05, 2011 - link

    Anand or Brian - any idea what carriers the 2x will be available on in the US? Reply
  • therealnickdanger - Wednesday, January 05, 2011 - link

    While I don't know anything officially (I don't think anyone does yet), LG brought its current Optimus line to all carriers. I would imagine that they will do the same with the 2X - assuming one carrier seeking exclusivity doesn't dump a pile of cash on LG's doorstep.

    If the LG Optimus (S, T, One) are any indication of the build quality of the 2X, then I will probably be in line to buy one as soon as it is made available on Sprint. I love my Optimus S.
    Reply
  • Cali3350 - Thursday, January 06, 2011 - link

    Probably the iPhone 4. When it comes to being smooth iOS is untouched at this point in time (probably because everything is GPU accelerated). Reply
  • Cali3350 - Thursday, January 06, 2011 - link

    Clearly posted in response to the wrong item, sorry. Reply
  • metafor - Wednesday, January 05, 2011 - link

    I think those are "throughput" numbers, not latency numbers. The technical reference manual:

    http://infocenter.arm.com/help/index.jsp?topic=/co...

    states "cycles" definition is merely the minimum number of cycles it takes to issue, not actually execute the instruction.

    VADD, for instance, takes 4 cycles for VFP (scalar) and 3 cycles for NEON/ASE (6 to writeback).
    Reply
  • Cali3350 - Wednesday, January 05, 2011 - link

    Have to say Im pretty wildly disappointed with how you guys seem to be mentioning it will be several months before this thing launches.

    I am desperately waiting for a new phone right now, but want the new tech. The HTC Mecha looks like it will be a killer phone but will still be running the same old Snapdragon HTC has used since the Incredible. I was really hoping either the Optimus or the Motorola Tegra 2 phone would be out by end of January/February, but that seems like its DEF not happening after reading this. That is all sorts of disappointment.
    Reply
  • aebiv - Wednesday, January 05, 2011 - link

    You mean the HD2 and the Nexus One... Incredible and EVO were late to the Snapdragon game. Reply
  • sirsoffrito - Thursday, January 06, 2011 - link

    I have a Droid Incredible. I beg to differ. Reply
  • solipsism - Wednesday, January 05, 2011 - link

    Is the die size different from the Cortex-A8? I’m wondering how this could affect placement in other smartphones. Reply
  • solipsism - Wednesday, January 05, 2011 - link

    Er, I mean in the dual-core variety. Reply

Log in

Don't have an account? Sign up now