I think there is a bit of misunderstanding - the OMAP3430 in the Droid is a SoC that contains not just the CPU and GPU, but also a DSP and an image processor. Looking at the break down pics, there is no separate GPU.
Also, part of the reason for under clocking is not just to save battery life, but also to extend the life of the processor. TI gives different MTBF ratings for the OMAP depending on the clock speed. So while it *can* do 600 MHz, it does significantly shorten the life of the chip. The OMAP36xx chips are built using a 45nm process and can do up to 1 GHz. The multicore OMAP4s can do over 1 GHz.
I think the Snapdragon will always be slightly behind in terms of performance - they are just releasing chips now that exceed the performance of the 2 year old OMAP3. The real advantage of these chips however is that they include the cellular modem and GPS onto a single package. This means devices using them can be made much smaller for comparable performance.
The DROID is using the Texas Instruments OMAP 3430 processor. This is very much a System-on-a-Chip design, including the ARM Cortex A8 CPU, the POWERVR SGX GPU, TI's IVA-2+ media processor (accelerates video encoding/decoding), and an image processor (primarily for camera input). The media processor and much of the other bits are enhanced versions of the modules in TI's DaVinci processor line, which have been in many if not most of the high-end PMPs lately (Archos, Cowon, etc)... at least before the nVidia Tegra came out.
It also includes nearly all the I/O needed in the system, aside from the radio/baseband processors themselves. See info here:
OMAP 3 Processors - OMAP3430
The iPhone 3GS is believed to use a version of the Samsung S5PC100 processor. Apple and Samsung have been mum about the iPhone specifics, but the S5PC100 is documented (see link). This has similar units for video, 3D, and image processing, as you might expect.
Only recent smart phones have this level of processor... the DROID, the iPhone 3GS, the Palm Pre (also uses the TI3430), maybe a few others. Older smart phones are more likely to use an ARM-11 or Marvell (formerly Intel, formerly formerly DEC) XScale (nee StrongARM) applications processor. The Cortex offers a much improved floating point unit, the NEON SIMD instruction set (like SSE on the x86), and 2-issue superscalar operation, versus single issue on the ARM-11 (both in-order).
I think the main confusion really comes from the amount of articles that more or less state one thing or another. Here are a few examples of what i mean.
According to both sites, the Droid packs in a speedy 550MHz Texas Instruments OMAP3430 processor with 256MB RAM and a separate PowerVR SGX GPU.There’s a 550MHz Texas Instruments OMAP3430 processor, separate PowerVR GPUThe phone will be powered by a OMAP3430 – 600 MHz ARM Cortex A8 with a PowerVR SGX 530 GPU and 430MHz C64x+ DSP + ISP (Image Signal Processor)All taken from separate websites.The Droid also includes a 550MHz Texas Instruments OMAP3430 processor, separate PowerVR GPU, 256MB of RAM
Resistance is futile.
On 11/16/2009 DroidNet Became Aware
Yeah, there's definitely a bit of confusion there. The reality is that none of the PowerVR designs have been available as separate chips for quite some time. They're only sold as IP cores, like ARM CPUs, which is why so many different manufacturers (TI, Samsung, Intel, etc) use these cores (Intel calls theirs the GMA500, but it's really an SGX535). For those interested in the history, a forerunner of the PowerVR was in the Sega Dreamcast video game console.
The DROID is clearly based on the SGX530, but I can't find mention of the clock speed -- also fairly meaningful when benchmarking a 3D pipeline. There have been accounts of both the SGX520 and the SGX535 being the version in the iPhone 3GS. Earlier iPhones used the MBX-Lite GPU at around 100MHz. However, the only mention in the context of the actual Samsung S5PC100 claims it's a SGX530 at 100MHz... same as in the OMAP3430. The SGX520 runs about 7 million polygons per second (about 3x to 7x faster than the regular iPhone)... assuming it's run at the full 200MHz possible for that core. The SGX530 doubles this, the SGX535 doubles it again.
The interesting thing is that, full screen, the iPhone 3GS only needs the SGX520 to keep pace with a DROID at full screen, since the DROID has 2.6x times as many pixels to paint. One possible source of the SGX535 story in the iPhone... there's a "IMGSGX535GLDriver" file, apparently the driver. Thing is, all versions of the SGX5xx use the same driver, so that's not necessarily reliable evidence.
The differences should be obvious, comparing a 3D benchmark of the older iPhone to the 3GS. Also interesting would be Android-based 3D benchmarks, though relating those to the iPhone (or other handhelds) would be curious, but not necessarily scaled well... there are plenty of system-level issues that could make one system or the other better here, not just the HW.
A quick look at 3GS benchmarks suggests the 3GS is doing 2x-4x the performance of the 3G on 3D benchmarks. That's more along the lines of what you'd expect out of the SGX520... or it's an indication the bottleneck lies elsewhere ... which would make the SGX535 pointless, anyway. Another benchmark (by Laszlo Kishonti) got 5.2 million triangles per second... which suggests either an SGX520 at 200MHz or an SGX530 at 100MHz. Hmmmm....
Overcloaking it from what i understood in many articles is not hard. It's keeping it cool at high Mhz frequencies that's hard, that and the amount of battery usage it uses.
Resistance is futile.
On 11/16/2009 DroidNet Became Aware