SAMSUNG HAS RELEASED two 1GHz ARM CORTEX-A8 based application processors.
The S5PC110 is targeted for small connected devices such as smartphones, while the S5PV210 is aimed at netbooks.
Samsung's Kwang Hyun Kim said that more PC power will be needed by mobile devices. This means that PC performance with lower power consumption will become a mainstream requirement for advanced mobile devices.
Kwang said that the S5PC110 and S5PV210 application processors will boldly enable a new level of user experience that apparently has never been boldly enabled before.
They can run on standard size batteries through a variety of low power technologies thanks to the company's 45nm Low Power fabrication process.
Each comes with 32KB data and 32KB instruction caches and a 512KB L2 cache. The 1GHz clock speed and relatively largish L2 cache means that these mobile processors can manage real-time web browsing and better user interfaces.
The S5PC110 and S5PV210 are equipped with a powerful built-in 3D graphics engine to better support 3D games. In addition, the two processors contain a full 1080p HD codec engine that supports 30fps full HD video playback and recording.
There is also a built-in HDMI1.3 interface that enables output of captured or downloaded mobile multimedia contents to an external HD digital display.
The S5PC110 is housed in a 0.5mm pitch, 14X14mm2 FBGA package that allows package-on-package vertical stacking of low power, multiple chip package (MCP) memory such as OneDRAM, mobile DDR and LP DDR2.
All this reduces the overall footprint of the memory and processor package so there are smaller muddy marks on the carpet.
The S5PV210 is packaged in a 0.65mm pitch, 17X17mm2 FBGA package with a high performance 2-channel 32-bit DDR2 memory interface.
These allegedly will get stuck into devices that will be in the shops by Christmas. µ
I can wait to see with Apple will bring us in their next iPhone.
@John - don't suggest that something like this might turn up in an iPhone or other Apple product. If Nick starts thinking that he'll go off on a rant about how the chip rapes babies and kills kittens and makes Jesus cry.
However 1080@30fps = 1080i and not 1080p.
The built in video and 3d sounds nice. If this platform is not tied to media content agreements and tied up drivers, this would be the platform to buy.
@Shhhhh - I have a theory... Nick is working for Apple! He complains about the "tame press" and he keep talking about Apple products!
With all the comments he posted on Apple, he help advertising their products!
I start loving good Apple products here!
:o)
John
Well if the processor doesn't suck this is a real chance for linux to get some traction. Unless MS has an arm version of windows 7, I'd say these netbooks are all going linux.... I don't think windows mobile is up to the task.
MS used to have windows for powerpc and other platforms, so they could certainly do it, but if these are out by Christmas I don't see it happening.
Trouble is, even with Windows on ARM there would be few if any applications as they are all x86 - they might come in time, but would the major app developers really want to support two architectures, one of which may be quite niche?
That's the advantage of Linux and open source applications, particularly Debian. The source is out there, you want it to run on a new esoteric hardware platform? Just build it yourself. Debian is ready to go on ARM with thousands of applications.
To someone above - who has mentioned that 1080p@30fps is actually 1080i - You are wrong. There is 1080P at 30Hz. The actual difference between P and I is if we are scanning every line in the picture (progressive) or alternate line (interlaced). Minimum requirement is to have it at 24fps (for human eye to not see it is a jerky image). So earlier to reduce the processing requirements - Interlaced scans were implemented. Now with improved processing capability - progressive is being implemented.
Most stuff people try to run on mobile devices has way too large working set for current chips' caches. Some have as little as 8kB instruction cache/8kB data cache. Couple that with a 16-bit data bus... Large L1 caches and huge (for a mobile device) 512kB L2 is very very welcome.