Welcome to the architecture page for ARM. This covers both ARMv7 (aka armhfp and arm-32) and aarch64 (aka ARMv8 and arm-64).
Fedora on ARM supports a wide variety of hardware from large enterprise aarch64 SBSA compliant hardware down to cheap single board computers (SBCs). We're primarily focused on Server, SBCs, IoT and other usecases that are similar to the Fedora Workstation / Server / Cloud that other Fedora architectures support.
The Fedora software stack experience across both the 32 and 64 bit ARM architecture variants is very similar, and in most cases identical, to what you would find on any other Fedora architecture. We use solely upstream kernels and don't use different kernels for each different ARM device we support.
The first starting point for ARM is the ARM Installation Guide.
Current stable release
The current stable release for ARMv7 can always be found at the ARM Image landing page
The current stable release for aarch64 can always be found at Alternate Architectures landing page
Current development releases
There are currently two development releases. Fedora 26 is in the stabilisation phase, Fedora rawhide (27) is in the development phase.
Supported Hardware and Devices
We support a wide variety of hardware and devices from numerous Single Board Computers (SBCs) like the Raspberry Pi 2 and 3 through to Chromebooks and SBSA compliant Servers.
Here is list of device pages based on device category or SoC:
- Raspberry Pi
- SBSA aarch64 Servers
- 96Boards devices
- All Winner based devices
- Marvell EBU based devices
- nVida Tegra based devices
- NXP i.MX6 based devices
- RockChips based devices
- STMicroelectronics based devices
- Samsing EXYNOS based devices
- Texas Instruments based devices
We don't directly support devices such as phones and tablets but it's not to say that without the required kernel/bootloader know how that they don't work, it's just not our primary focus.
Get Involved with Fedora ARM
- IRC: Every Tuesday at 16:00 UTC.
Scratch an itch
All architectures are now integrated into the standard Fedora process. We don't diverge in any way. So without even realising everyone is already involved. To get involved in something more specific whether that's support for particular pieces of hardware or hardware feature, a particular piece of software, to help test or to scratch an itch a good spot to start is the mailing list or IRC channel.
Bugs should be reported against their prospective packages as per standard Fedora process. Add a blocker of "ARMTracker" which will link to our ARM architecture tracker bug. If the bug is on a pre release version of Fedora and you feel it's release affecting it might be considered a Blocker Bug or Freeze Exception in which case it should be reported in the QA Blocker bug app.