Talk:ARM Cortex-A15

5x misnomer
Up to 5 times faster? Doubtfull: the multiple ALU and complex schedulers are power-expensive hardware -- so, how ARM could get 5x speedup? At least, reference needed.

According to this: http://www.bdti.com/InsideDSP/2010/10/19/arm -- dual core A15 will be 5x time faster than current single-core Cortex-A8, not Cortex-A9 MPCore. —Preceding unsigned comment added by 87.224.226.88 (talk) 18:14, 8 February 2011 (UTC)


 * "15-stage out-of-order speculative issue superscalar execution pipeline, providing up to 5 times the performance of Cortex-A9 MPCore. ARM confirmed that the Cortex A15 core is 40 per cent faster than the Cortex A9 core, all things equal."


 * I'd like to get rid of the "up to 5 times" part, but thought it might be worth discussing because it isn't pure FUD. ARM actually has a graph where they divide up types of workloads on the chip compared to the A8 I think, and in the best workload segment it is something like 5 times better. Nvidia noted that their Kal El processor (Tegra 3) has been overclocked and fine tuned to the point that it is twice as fast as their Tegra 2 (both A9s), and that the graphics is 3 times faster, and has been pushing the "5 times better" mantra (such as in the famous logarithmic graph) for sound marketing reasons — but this is really a 2x + 3x = 5x, and not an outright 5 times faster performance.


 * I think this has an unfortunate resonance in the A9 to A15 comparisons, and many sources mistaken apply a "5 times better" label to a chip that is 40-50% faster, clock for clock, and also about 50% less in power. Still, if you assume that the 2Ghz design max for the A9 was overly optimistic (as no one has achieved it in practice) and compare a theoretical a15 @ 2.5Ghz to a run-of-the-mill A9 @ 1Ghz, the potential is maybe nearing 5x performance, definitely north of 2.5x performance which you can multiply out against the power savings to get a 5x performance over watts.


 * Anyone else agree that the "5-times the performance" blurp can go? It's a whole lot to take in if we were to go the other way and try to clarify where those numbers come from.


 * edit: after noticing all the above comments and repositioning my post with them, I'm going to take the plurality of similar opinions here as reason enough to go ahead proactively and remove the blurb. --—  r obbie  page talk 18:51, 24 May 2011 (UTC)

how many bits?
It would be nice if the specs listed whether this is a 32 or 64 bit CPU. —Preceding unsigned comment added by 95.209.23.48 (talk) 17:56, 26 April 2011 (UTC)


 * ARM is a 32 bit only processor architecture. You can have a 32 bit CPU that breaks the 4GB addressing barrier by adding extra address bits called PAE (physical address extension). Essentially the extra bits multiply the 4GB address space into multiple blocks of 4GB. The OS takes care of the rest. Intel started this with their Pentium Pro by adding 4 extra bits creating a 36 bit address bus. This allowed the OS to address upward of 64GB of memory, though Microsoft limited this to 4GB to desktop versions of Windows. Only certain 32bit server Operating systems from Microsoft were allowed to utilize PAE. Linux of course has no such restrictions and any user can take full advantage of PAE. 24.186.130.27 (talk) 15:08, 16 June 2011 (UTC)


 * Precise and good explaination. Thanks 24.186.130.27! :) 84.112.79.216 (talk) 15:06, 6 July 2011 (UTC)


 * ARMv8, announced 2011 October, is 64 bits. 24.186.130.27 could not have known the future four months ahead of time, but it is always unwise to say "ARM is only ". Fnj2 (talk) 21:08, 18 December 2011 (UTC)

LPAE
The memory addressing is 40-bit, not 64-bit. You do need to go above 32-bit to get a full 1TB, but does that mean they actually implemented, and then gimped, a full 64-bit implementation? --—  r obbie  page talk 18:09, 24 May 2011 (UTC)
 * If I recall correctly, they have some extra room left in their new page table format to grow the physical address. You'll have to register on ARM's site to get the docs for the details, though.  I can understand why they might stop at 40 bits, though.  Cache tags for a physically indexed cache would be over twice the size with 64-bit physical addresses vs. 40-bit physical addresses, so somehow I doubt they implemented a 64-bit design and hobbled it.  Heck, even AMD's x86-64 extensions stopped at 48 bits of physical address. --Mr z (talk) 15:51, 17 November 2011 (UTC)

Requesting input
The popularity of the Cortex M0 and M4 are starting to take off, thus it would be easier to pick some direction before having a bunch of tiny articles. Should there be unique articles for each of the ARM Cortex families? Should there be only 3 major ARM Cortex articles instead, and redirect all sub-flavors to these 3 new articles? Requesting input at Talk:List of ARM microprocessor cores for comments! • Sbmeirow  •  Talk  •  17:14, 5 December 2011 (UTC)

ARM Cortex-A15 lacks an integer hardware division instruction
Does anyone have evidence that any Cortex-A15 chips have an integer hardware division instruction? The GNU compiler isn't proof of what is inside of the silicon. • Sbmeirow  •  Talk  •  14:26, 11 January 2012 (UTC)
 * ARM Cortex-A15 lacks an integer hardware division instruction
 * Slide 9 here indicates that the processor supports an integer divide instruction (and slide 27 indicates that it is implemented in the multiply/divide execution cluster). Jakew (talk) 14:48, 11 January 2012 (UTC)

It's now a moot point anyway, as the referenced page was edited to mention some new ARM processors do support division in hardware. ZPedro (talk) 22:10, 12 December 2012 (UTC)

Samsung Chromebook & Exynos5250
I think the Exynos will be available soon. Google/Samsung wouldn't announce their Chromebook if it takes half a year before shipment. — Preceding unsigned comment added by 84.106.240.13 (talk) 10:09, 19 October 2012 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on ARM Cortex-A15. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20120417183714/http://www.arm.com/files/downloads/big.LITTLE_Final.pdf to http://www.arm.com/files/downloads/big.LITTLE_Final.pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 08:57, 1 October 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on ARM Cortex-A15. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added tag to http://pressroom.nvidia.com/easyir/customrel.do?easyirid=A0D622CE9F579F09&version=live&releasejsp=release_157&xhtml=true&prid=705184
 * Added archive https://web.archive.org/web/20130618091608/http://stericsson.com/press_releases/NovaThor.jsp to http://www.stericsson.com/press_releases/NovaThor.jsp
 * Added archive https://web.archive.org/web/20130719172028/http://www.geekbuying.com/item/Freelander-PD800HD-Dual-Core-Exynos-5250-Android-4-2-Tablet-PC-9-7--Retina-Capacitive-Touch-Screen-2048-1536-2GB-16GB-BT-White-315165.html to http://www.geekbuying.com/item/Freelander-PD800HD-Dual-Core-Exynos-5250-Android-4-2-Tablet-PC-9-7--Retina-Capacitive-Touch-Screen-2048-1536-2GB-16GB-BT-White-315165.html
 * Added archive https://web.archive.org/web/20131002062352/http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G137510300620 to http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G137510300620&tab_idx=2
 * Added archive https://web.archive.org/web/20140815080514/http://www.samsung.com/us/computer/chrome-os-devices/xe503c12-k02us/ to http://www.samsung.com/us/computer/chrome-os-devices/XE503C12-K02US

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 04:58, 24 June 2017 (UTC)