Nothing is new about the Atom core architecture in Medfield (besides much lower power, especially in standby, on a 32nm LP process), but AT has a pretty good overview of the new single core with HT SoC design. Power consumption is pretty impressive:
Medfield CPU Frequency vs. Power (SoC Power Consumption)
100MHz ~50mW
600MHz ~175mW
1.3GHz ~500mW
1.6GHz ~750mW
Smartphone power consumption (whole phone)
3G standby ~18mW*
talk 3G ~700mW
browsing 3G ~1.0W*
video playback 720p ~850mW
* lower power than iPhone 4S and Galaxy S II
Unfortunately only browser benchmarks and simple graphics test results were shown. The CPU performance is great on web browser benchmarks vs dual core A9. Graphics performance isn't bad, but it's also nothing great (SGX540 @ 400MHz). The test platform is running Gingerbread, but phones with Medfield are expected to run ICS.
OK, Android... how will x86 run ARM apps? Interesting answer:
Medfield CPU Frequency vs. Power (SoC Power Consumption)
100MHz ~50mW
600MHz ~175mW
1.3GHz ~500mW
1.6GHz ~750mW
Smartphone power consumption (whole phone)
3G standby ~18mW*
talk 3G ~700mW
browsing 3G ~1.0W*
video playback 720p ~850mW
* lower power than iPhone 4S and Galaxy S II
Unfortunately only browser benchmarks and simple graphics test results were shown. The CPU performance is great on web browser benchmarks vs dual core A9. Graphics performance isn't bad, but it's also nothing great (SGX540 @ 400MHz). The test platform is running Gingerbread, but phones with Medfield are expected to run ICS.
OK, Android... how will x86 run ARM apps? Interesting answer:
Well, that's a leg up on the MIPS Android devices.Intel believes that roughly 75% of all Android apps in the Market don't feature any native ARM code. The remaining 25% are the issue. The presumption is that eventually this will be a non-issue (described above), but what do users of the first x86 Android phones do? Two words: binary translation.
Intel isn't disclosing much about the solution, but by intercepting ARM binaries and translating ARM code to x86 code on the fly during execution Intel is hoping to achieve ~90% app compatibility at launch. Binary translation is typically noticeably slower than running native code, although Intel is unsurprisingly optimistic about the experience on Android. I'm still very skeptical about the overall experience but we'll have to wait and see for ourselves.