The Partners and the Landscape

Although NVIDIA announced the Tegra 2 at CES 2010, it wasn’t until CES 2011 that we saw a single smartphone design win. Luckily for NVIDIA, we got two wins at this year’s CES: LG and Motorola.

Here’s how the landscape breaks down. In 2011 TI will have its OMAP4, used in the BlackBerry Playbook tablet and Qualcomm has its Snapdragon QSD8660. The QSD8660 will be used in upcoming HP/Palm and HTC devices later this year.

2011 SoC Landscape
NVIDIA TI Qualcomm
Handset Partners LG
Motorola
Samsung (?)
RIM/Blackberry
Nokia (?)
Dell
HTC
Huawei
Sony Ericsson

This leaves us with Dell, Huawei, Nokia, Samsung and Sony Ericsson. Dell, Huawei and Sony Ericsson are all in Qualcomm’s camp. I’d expect that to continue. Nokia has shipped TI SoCs in the past, and I’d expect that to continue as well (if not TI, then Intel). That leaves us with Samsung. Samsung has typically shipped its own SoCs, however the recently announced Orion is still far from ready. With a hole in its roadmap, Samsung is rumored to be in NVIDIA’s camp for its next generation of Galaxy devices. And I don’t like posting rumors on AT.

All of the aforementioned SoC vendors have key design wins. NVIDIA went from being a no-show to a key player in the smartphone and tablet space. Did I mention that NVIDIA’s Tegra 2 is the reference SoC for Android 3.0 (Honeycomb)?

NVIDIA’s roadmap ahead is equally impressive. NVIDIA secrets are leaking left and right, perhaps on purpose. At MWC 2011 NVIDIA is expected to announce the successor to the Tegra 2: the NVIDIA Tegra 2 3D. And late this year or at CES 2012, NVIDIA is expected to announce Tegra 3. Two new Tegra SoCs within a 12 month period? PC gaming veterans should recognize a very familiar pattern. NVIDIA looks to be bringing back the 6-month product cycle.

Frustratingly good execution is what helped establish NVIDIA in the PC GPU industry, and ultimately what drove competitors like 3dfx and Matrox out. Based on the leaked roadmaps, it looks like NVIDIA is trying to do the same thing with smartphone SoCs.

Tegra 2, Tegra 2 3D and Tegra 3 are all 40nm parts, and only Tegra 3 is a new architecture (GPU, not CPU). This is a deviation from NVIDIA’s old 6-month cadence, but we’ll see what Tegra 3 Ultra/Tegra 4 bring in 2012. If the follow up to Tegra 3 is a 28nm shrink, followed by a new architecture with Tegra 4 by the end of 2012/beginning of 2013 then NVIDIA may truly be up to its old tricks. But for now it’s too early to tell as Tegra 2 3D looks to just be a clock bump of Tegra 2.

Based on what’s been made public thus far, the Tegra 2 3D will add glasses-free 3D support (LG has already announced that it’ll be showing off the world’s first 3D smartphone at MWC 2011). Tegra 3D will also bump clock speeds from 1GHz to 1.2GHz. This boost is important as it’ll match Qualcomm’s QSD8660, which will ship at up to 1.2GHz

Little is known about Tegra 3. Based on the timing I’m guessing it’ll still be Cortex A9, however with some performance tweaks (and a faster/beefier GPU). NVIDIA has the design wins and it has the roadmap going forward.

The GeForce ULV Performance: Android and Multithreading
Comments Locked

75 Comments

View All Comments

  • djgandy - Monday, February 7, 2011 - link

    It'll be interesting to see how all the other SoC's perform with DDR2.
  • DanNeely - Monday, February 7, 2011 - link

    Where can I find more information on this?
  • Anand Lal Shimpi - Monday, February 7, 2011 - link

    Here's a link to the immediate mode vs. tbdr discussion in our old Kyro II review:

    http://www.anandtech.com/show/735/2

    Take care,
    Anand
  • silverblue - Monday, February 7, 2011 - link

    I'm not sure I agree with the wording in this article about TBDR. The reason PowerVR didn't need to slap DDR RAM onto the Kyro II cards is because they simply didn't need it thanks to the reduction of traffic that comes from deferred rendering. The unknown element at the time was hardware T&L because it simply wasn't available and was thought to be impossible, however as this is yet again being performed on-die, wouldn't that also result in a marked reduction in traffic? Might need some clarification on this one.

    I've never seen it confirmed that the Adreno GPU performs TBDR; some clarification would be appreciated on this one as well! :)

    Onto the option for changing fonts... my vendor-agnostic Galaxy S has such a feature called "Font style" under the Display settings, allowing you to choose the "Default font", "Choco cooky", "Cool jazz" and "Rosemary", with the option of getting more online.
  • Exophase - Monday, February 7, 2011 - link

    Qualcomm bought out AMD's mobile GPUs and hence the Adreno 200 was a rebrand of AMD z430. Here's a little more background on the tiling nature of z430:

    (since apparently I can't post a link without being flagged as spam just google for this: gdc2008_ribble_maurice_TileBasedGpus.pdf - it's the first hit)
  • silverblue - Monday, February 7, 2011 - link

    Interesting... I'd like to see the differences between their approach and that of Imagination Technologies.
  • silverblue - Monday, February 7, 2011 - link

    Thanks by the way... answered a lot of questions. :)
  • AndroidFan - Monday, February 7, 2011 - link

    should be 300mhz (=600/2)
  • Zaitsev - Monday, February 7, 2011 - link

    Is the camera really too thick to fit the width of the phone? I heard of many Evo users who have cracked the glass covering. While I haven't had this problem, it makes me wonder if it's really necessary in the first place.

    Thanks
  • MeSh1 - Monday, February 7, 2011 - link

    I cant wait until you can wirelessly shoot your phones display to your tv ala intel WiDi. This HDMI out is cool, but the cable kind of kills it. With wireless display your phone becomes a game controller :) or a remote when shooting movies to your tv. Plus how cool would it be if your phone can fetch movies from your home network and you shot the playback to your TV. The Sony NGP should have implemented this. Ah well.

Log in

Don't have an account? Sign up now