Application ARM-based chips |
|---|
|
Application processors (32-bit) | | Cortex-A5 | |
|---|
| Cortex-A7 |
- Allwinner A2x, A3x, A83T, H3, H8
- Freescale i.MX7
- Broadcom VideoCore BCM2836, BCM23550
- Freescale QorIQ LS10xx
- Leadcore LC1813, LC1860/C, LC1913, LC1960
- Marvell Armada PXA1920, 1500 mini plus
- MediaTek MT65xx
- Qualcomm Snapdragon 200, 400
|
|---|
| Cortex-A8 | |
|---|
| Cortex-A9 |
- Actions ATM702x, ATM703x
- Altera Cyclone V, Arria V/10
- Amlogic AML8726, MX, M6x, M801, M802/S802, S812, T86x
- Apple A5, A5X
- Broadcom VideoCore BCM21xxx, BCM28xxx
- Freescale i.MX6
- HiSilicon K3V2, 910's
- InfoTM iMAPx912
- Leadcore LC1810, LC1811
- Marvell Armada 1500 mini
- MediaTek MT65xx
- Nvidia Tegra, 2, 3, 4i
- Nufront NuSmart 2816M, NS115, NS115M
- Renesas EMMA EV2, R-Car H1, RZ/A
- Rockchip RK292x, RK30xx, RK31xx
- Samsung Exynos 4 421x, 441x
- ST-Ericsson NovaThor
- Telechips TCC8803
- Texas Instruments OMAP 4
- Texas Instruments Sitara AM4xxx
- VIA WonderMedia WM88x0, 89x0
- Xilinx Zynq-7000
- ZiiLABS ZMS-20, ZMS-40
|
|---|
| Cortex-A15 | |
|---|
| Cortex-A17 | |
|---|
ARMv7-A compatible |
- Apple A6, A6X, S1, S1P, S2, S3
- Broadcom Brahma-B15
- Marvell P4J
- Qualcomm Snapdragon S1, S2, S3, S4 Plus, S4 Pro, 600, 800 (Scorpion, Krait)
|
|---|
| Others | |
|---|
|
|---|
Application processors (64-bit) | | Cortex-A53 |
- Actions GT7, S900, V700
- Allwinner A64, H5, H64, R18
- Altera Stratix 10
- Amlogic S9 Family, T96x
- Broadcom BCM2837
- EZchip TILE-Mx100
- HiSilicon Kirin 620, 65x, 93x
- Marvell Armada PXA1928, Mobile PXA1908/PXA1936
- MediaTek MT673x, MT675x, MT6795, MT873x, MT8752, MT8163
- NXP ARM S32
- Qualcomm Snapdragon 41x, 42x, 43x, 61x, 62x
- Rockchip RK3328, RK3368
- Samsung Exynos 7 75xx, 78xx
- Spreadtrum SC9860/GV, SC9836
- Xilinx ZynqMP
- Freescale QorIQ LS1088
|
|---|
| Cortex-A57 | |
|---|
| Cortex-A72 | |
|---|
| Cortex-A73 | |
|---|
ARMv8-A compatible | |
|---|
| Others | |
|---|
|
|---|
Initial visibility: currently defaults to autocollapse
To set this template's initial visibility, the |state= parameter may be used:
|state=collapsed: {{Application ARM-based chips|state=collapsed}} to show the template collapsed, i.e., hidden apart from its title bar
|state=expanded: {{Application ARM-based chips|state=expanded}} to show the template expanded, i.e., fully visible
|state=autocollapse: {{Application ARM-based chips|state=autocollapse}}
- shows the template collapsed to the title bar if there is a
{{navbar}}, a {{sidebar}}, or some other table on the page with the collapsible attribute
- shows the template in its expanded state if there are no other collapsible items on the page
If the |state= parameter in the template on this page is not set, the template's initial visibility is taken from the |default= parameter in the Collapsible option template. For the template on this page, that currently evaluates to autocollapse.