Segars stressed that the ARMv8 instruction set architecture also supports both the Aarch64 mode and an Aarch32 mode. The later provides compatibility with the 32-bit ARMv7 instruction set.
ARM also is betting that security features will grow in importance across the range of applications it expects A57 and A53 to address. "TrustZone security features are present in ARMv7 and they have been carried forward in ARMv8. We have added instructions [in ARMv8] that will provide 10 times the encryption performance," said Greenhalgh.
Segars added that while the need for 64-bit data and addressing may not yet be present in mobile client devices, ARM's partners are pressing for the capability as part of preparation for a changeover from 32- to 64-bit processing. "That change is more rapid in enterprise applications and somewhat slower in mobile," he said.
The overwhelming need for more memory is only growing. ARM's software partners are supporting the requirement with an announcement from Redhat and the fact that a 64-bit Linux kernel is available to developers, Segars said.
As expected, the A57 and A53 make use of the CCN-504 cache coherency networking IP and Amba bus interfaces licensed by ARM. It is compatible with ARM's Mali graphics IP.
ARM expects to have processor silicon in house sometime as early as mid-2013. "Although ARM partners will usually beat to us to silicon," Greenhalgh added.
Part of the issue is that:
because ARM is developing IP for licensing to semiconductor partners it has to be a couple of years ahead of those semiconductor partners.
When ARM announced Cortex-A7 and the big-little approach in Oct. 2011 the company said tape-outs including the Cortex-A7 were expected 1H12 with SoCs and products based on them to follow in 2013, East said.
Seems like ARM and partners are not late on that timetable...yet!
Yep i wud 2nd that notion! D current drastic improvements in processing power mean little or nothng wthout commensurate improvements in power efficiency n battery life! All the smartphone n handheld device specs these days r getting bloated without any1 focusing proper attention on d most basic thing wich runs it all- the battery! ARM seems 2 hav at least partially addressed the problem with their big.Little approach but we're yet to see any real chip implementation of a big.Little part for the 1st generation n v alrdy hav an announcement of 2nd gen big.Little processors! Somethng dsnt add up here! ARM n Samsung where r d 1st gen big.Little SOCs featuring Cortex A15-A7 pairs???
Good luck putting Exynos5 as it is at 1.5GHz in a smartphone. The battery will last 2 hours. Rick, I thought you are smarter than what you are saying here. Putting A57 in a mobile phone. Good luck. Why not put AMD Trinity into a phone, then. i think your gray hair is covering your brain from working or may be you are too old for this
Samsung's Exynos 5 dual uses two A15 cores.
ARM says the first big/little SoCs won't be ready until early next year. Some of the sw for it is still in development though early test results are promising.
At Samsung's keynote, the chip exec talked about its dual core Exynos 5, presumably with an A15 and A7 made in a 32 nm HKMG process.
It uses ARM Mali T604 graphics core supporting OpenCL.
The SoC is in the new Google Chromebook and Galaxy 10 Tab amd a Quanta ultra thin ODM tablet design.
"I'd love to hear anyone's thoughts about how initially mobile developers might try to use this 64-bit capability."
Smartphones already have 2G of DRAM. And there is a lot of feature growth (and bloat) with every new generation. It won't be long before that memory doubles, and then you've exceeded your 32 bit processor memory space.
All we seem to be getting at present r future projections of more advanced chips (read Cortex A57-A53)which r still a good year n half away but v r yet to get any practical implementations of the 1st gen Cortex A15-A7 big.Little chips which hav been long announced!
Join our online Radio Show on Friday 11th July starting at 2:00pm Eastern, when EETimes editor of all things fun and interesting, Max Maxfield, and embedded systems expert, Jack Ganssle, will debate as to just what is, and is not, and embedded system.