[Ernest_at_the_Beach]

fyi

[Ernest_at_the_Beach]

Adding this:

*************************************EXCERPT****************************************

The CPU: A Dual-Core ARM Cortex A9

 

NVIDIA is a traditional ARM core licensee, which means it implements ARM’s own design rather than taking the instruction set and designing its own core around it (ala Qualcomm). 

 

The Tegra 2 SoC has a pair of ARM Cortex A9s running at up to 1GHz. The cores are clock gated but not power gated. Clock speed is dynamic and can be adjusted at a very granular level depending on load. Both cores operate on the same power plane.

[ShadowAce]

[astyanax]

"You’ll simply connect your smartphone to a wireless display and keyboard/mouse when you’re at your desk..."
As Scotty said, "How quaint."
The next-gen models will simply project a virtual keyboard onto your desk and a holographic image above your phone. ;)

[Ernest_at_the_Beach]

Mentioned in the article:

Motorola Atrix 4G, HD multimedia dock, and laptop dock hands-on

[antiRepublicrat]

I recently read about Android’s display model. Apparently its way out of date, always compositing the screen image in software on the CPU. So no matter how good your GPU is, you’re still stuck draining battery and getting lower performance than you could have. In comparison, iOS composites your screen on the GPU, and I bet WP7 does it too.

Defenders of this method say it’s needed because of the low-end Android devices on the market that can’t composite on the GPU. However, the technology to fall-back on CPU when sufficient GPU isn’t available has been around for years. Then the argument is made that having a fallback makes things more difficult for the developer. However, auto-fallback has also existed for years, where the developer writes code to draw something and the OS will decide whether it can be done on the CPU or GPU, and take the appropriate route.

So now you have this awesome chipset, but hindered by the OS.