Latest revision as of 09:37, 16 April 2024

Shortcut: Arch:ARM

Shortcut: Arch:AArch64

Have a question?
Join the Fedora ARM team on IRC in #fedora-arm^[?] on Libera

Introduction

Welcome to the architecture page for ARM. Note Fedora no longer supports ARMv7 (aka armhfp, aarch32, and arm-32), only aarch64 (aka ARMv8 and arm64).

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 Servers, SBCs, IoT, and other use cases similar to the Fedora Workstation / Server / Cloud that other Fedora architectures support.

The Fedora software stack experience on the 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 a single upstream kernel for all devices. Users of hardware that supports both 32-bit and 64-bit (A53/A72/etc) environments must use aarch64 images.

Getting started

The first starting point for ARM is the ARM Installation Guide.

Download

Current stable release

The current stable release for aarch64 can be found at Get Fedora

Platforms that should work since the F35 timeframe Fedora 35 Hardware Status

Current development release

The development release is Fedora Rawhide:

Fedora Rawhide (AArch64 only)

Supported Hardware and Devices

We support a wide variety of hardware and devices from numerous Single Board Computers (SBCs) like the Raspberry Pi 3 and 4 to Chromebooks and SBSA compliant servers.

Here is a list of device pages based on device category or SoC:

We don't directly support devices such as phones and tablets, but it's not to say that without the required kernel/bootloader they don't work; it's just not our primary focus.

Supported Hardware Addons

Get Involved with Fedora ARM

Communication

Mailing list: arm (archives)
IRC: #fedora-arm^[?] on https://libera.chat/

Meetings

IRC: #fedora-meeting-2^[?] Every Tuesday at 15: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 realizing 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.

Bug Reporting

Bugs should be reported against their prospective packages as per the 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.

Getting help with ARM build issues

The best place to get help with ARM issues is on #fedora-arm on Libera. The Fedora users and developers from around the world will assist when they are available but due to the many time zones, your question may not be answered right away so its best to remain in the channel. You can also email the Fedora ARM mailing list for assistance.

@@ Line 1: / Line 1: @@
 {{shortcut|Arch:ARM}}
+{{shortcut|Arch:AArch64}}
+{| style="width: 50%; float: right; margin-left: 2em;"
+|-
+| style="border-width: 0;" | {{admon/tip | Have a question? | Join the Fedora ARM team on IRC in {{fpchat|#fedora-arm}} on [https://libera.chat Libera]
+}}
+|}
-[[File:091-IMG_4134.JPG.medium.jpeg|right|300px|thumb|Examples of ARM develoment systems, including a SheevaPlug (white box), GuruPlug (black box), [http://en.wikipedia.org/wiki/BeagleBoard BeagleBoard] (bare PCB), and OpenRD-Client (silver box). These systems typically consume under 5 watts each.]]
 = Introduction =
-ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, and are increasingly used in tablet devices and low-power-consumption servers.
-The Fedora-ARM project is an initiative to bring Fedora to this processor family.
+Welcome to the architecture page for ARM. Note Fedora no longer supports ARMv7 (aka armhfp, aarch32, and arm-32), only aarch64 (aka ARMv8 and arm64).
-= Communication =
+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 Servers, SBCs, IoT, and other use cases similar to the Fedora Workstation / Server / Cloud that other Fedora architectures support.
-* Mailing list: [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org] ([http://lists.fedoraproject.org/pipermail/arm/ archives])
-* IRC: [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]
-= Resources =
+The Fedora software stack experience on the 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 a single upstream kernel for all devices. Users of hardware that supports both 32-bit and 64-bit (A53/A72/etc) environments must use aarch64 images.
-Detailed information on Fedora-ARM:
-* [[Architectures/ARM/Using|Running Fedora-ARM on your ARM device, or through emulation on your PC]]
-* [[Architectures/ARM/Package Maintainers|Information for Fedora package maintainers on getting your packages to work on ARM]]
-* [[Architectures/ARM/Team and Developers|Information for Fedora-ARM team members (and prospective team members!) plus developers]]
-* [[Architectures/ARM/CrossToolchain|How to get an armv5tel cross toolchain installed on your x86 Fedora host]]
-* [[Architectures/ARM/Building a Kernel for ARM|How to build a kernel and cross-compile for ARM]]
-* [[Architectures/Fedora_ARM_Kernels|Building and Installing a Fedora Kernel Package on ARM Systems]]
-= Releases =
+== Getting started ==
-* F13 (Alpha)
-** [http://lists.fedoraproject.org/pipermail/arm/2011-May/001271.html Fedora 13 Beta 3 release for ARM] (latest)
-** [[Architectures/ARM/F13-ARM-Beta2|Fedora 13 Beta 2 release for ARM]] (obsolete)
-** [[Architectures/ARM/F13-ARM-Beta1|Fedora 13 Beta 1 release for ARM]] (obsolete)
-* F12
-** [[Architectures/ARM/Release/12|Fedora 12 release for ARM ]]
-<!--
+The first starting point for ARM is the [[Architectures/ARM/Installation | ARM Installation Guide]].
-----
+== Download ==
-'''OLD PAGE CONTENTS HERE'''
+=== Current stable release ===
--- page was renamed from ARM --
-= Fedora ARM =
-This is the starting page for the Fedora port to the ARM architecture.
+* The current stable release for aarch64 can be found at [https://getfedora.org/ Get Fedora]
+* Platforms that should work since the F35 timeframe [[ Architectures/ARM/Fedora_Linux_35 | Fedora 35 Hardware Status ]]
-== Goals and Objectives ==
+=== Current development release ===
-The primary goal of this project is to provide support for ARM as a [[TomCallaway/SecondaryArchitectures|  secondary architecture]]  in Fedora.
+The development release is Fedora Rawhide:
-A secondary goal is to enable derivative distributions based on the Fedora package collection and repository that are more suitably optimized for embedded and mobile use-cases.
+* [https://download.fedoraproject.org/pub/fedora/linux/development/rawhide/ Fedora Rawhide (AArch64 only)]
-== Technical Approach ==
+== Supported Hardware and Devices ==
-=== Native Compilation ===
+We support a wide variety of hardware and devices from numerous Single Board Computers (SBCs) like the Raspberry Pi 3 and 4 to Chromebooks and SBSA compliant servers.
-Fedora policy requires that packages be natively compiled. We use a cluster of ARM hardware and QEMU virtual machines to build the packages natively for ARM.
+Here is a list of device pages based on device category or SoC:
-=== CPU and Architecture Target ===
+* [[Architectures/ARM/Raspberry_Pi|Raspberry Pi]]
+* [https://docs.fedoraproject.org/en-US/fedora/latest/install-guide/  SBSA and SystemReady machines]
+** [[Architectures/ARM/LX2160A|Honeycomb LX2/Clearfox CX LX2 devices]]
+** [[Virtualization targets, Hyper-V, EC2]]
+* [[Architectures/ARM/96Boards|96Boards devices]]
+* [[Architectures/ARM/AllWinner|All Winner based devices]]
+* [[Architectures/ARM/mvebu|Marvell EBU based devices (64-bit 7k8k+)]]
+* [[Architectures/ARM/Tegra|nVidia Tegra based devices]]
+* [[Architectures/ARM/RockChips|RockChips based devices]]
+* [[Architectures/ARM/Qualcomm|Qualcomm]] including laptops
+** [[Thinkpad_X13s|Lenovo X13s (WIP)]]
+* [[Architectures/ARM/exynos|Samsung EXYNOS based devices]] e.g., Odroid XU4
+* [[Architectures/ARM/TI|Texas Instruments based devices]]
+** [[BeaglePlay|BeaglePlay]]
+** [[SK-AM69|SK-AM69 Starter Kit]]
+* [[Architectures/ARM/Xilinx|Xilinx ZynqMP based devices]]
-The baseline ARM CPU architecture that we have chosen to support is ARMv5TE, Little Endian, Soft-Float, EABI. We believe that this provides a nice baseline and that the pre-built packages and root file system images. You should be able to use this on many of the modern ARM CPUs, including XScale, ARM926 and ARM-11, etc.
-Although we do not provide such binaries, the sources also lend themselves for building for pre-ARMv5TE hardware. The same is true for big-endian CPUs.
+We don't directly support devices such as phones and tablets, but it's not to say that without the required kernel/bootloader they don't work; it's just not our primary focus.
-=== Installer and Kernel ===
+= Supported Hardware Addons =
+* [[Architectures/ARM/i2c|i2c and devices attached to i2c]]
+* [[Architectures/ARM/gpio|Using the GPIO]]
-We currently do not plan to provide an installer, ISO images, or a kernel. Unlike in the x86 world, different ARM CPU families require different kernel images. Likewise, it is not entirely clear whether it makes sense to provide an installer or ISO images.
+= Get Involved with Fedora ARM =
-== Contribute ==
+=== Communication ===
-* This is a tracking page for packages requiring patching to build on ARM: [[Architectures/ARM/Packages_needing_patching]]
-!-- * A list of builds that are failing on ARM architecture is maintained [http://arm.koji.fedoraproject.org/packages_to_be_fixed.html here]. It is a good starting point for anyone willing to contribute to the Fedora-ARM project. The list is updated daily. --
-* We have a [[Architectures/ARM/TODO|TODO list]].
-* Have a look at the [[Architectures/ARM/Credits| Credits page]]
-* Fedora ARM is currently heavily driven by the Seneca Centre for Development of Open Technology (CDOT) at the School of Computer Studies at Seneca College, Toronto. More information about their status can be found in the [http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture CDOT ARM wiki]
-=== How to get in touch? ===
+* Mailing list: {{fplist|arm}} ([https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/ archives])
-* The [https://admin.fedoraproject.org/mailman/listinfo/arm Fedora-ARM mailing list]  is available for both user and developer discussions.
+* IRC: {{fpchat|#fedora-arm}} on https://libera.chat/
-* We also have an IRC channel #fedora-arm on Freenode.
-* Frequent updates about the effort are available at [http://paulfedora.wordpress.com Paul Whalen's ARM blog]
-* Some old postings from November 2009 and earlier are available at the [http://fedora-arm.blogspot.com Fedora-ARM blog]
-=== Tracker Bugs ===
+=== Meetings ===
-If excluding ARM architectures you need to make the bug block '''F-ExcludeArch-ARM'''
+* IRC: {{fpchat|#fedora-meeting-2}} Every Tuesday at 15:00 UTC.
-to see whats currently blocking visit [https://bugzilla.redhat.com/show_bug.cgi?id=F-ExcludeArch-ARM  Bugzilla ]
+=== Scratch an itch ===
+All architectures are now integrated into the standard Fedora process. We don't diverge in any way. So without even realizing 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.
-If a bug is specific to ARM architectures make the bug blocking '''ARMTracker'''
+=== Bug Reporting ===
+Bugs should be reported against their prospective packages as per the standard Fedora process. Add a blocker of "ARMTracker" which will link to our [https://bugzilla.redhat.com/show_bug.cgi?id=245418 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 [[QA:SOP_blocker_bug_process|Blocker Bug]] or [[QA:SOP_freeze_exception_bug_process|Freeze Exception]] in which case it should be reported in the [https://qa.fedoraproject.org/blockerbugs/ QA Blocker bug app].
-to see not yet resolved issues visit [https://bugzilla.redhat.com/show_bug.cgi?id=ARMTracker  Bugzilla ]
+=== Getting help with ARM build issues ===
-=== Package Maintainer Notes ===
-As part of setting up to be a package maintainer, you should have run fedora-packager-setup from the fedora-packager rpm. That will write secondary arch config files in ~/.koji. To kick off a build for a package you maintain, run:
-<pre>
-make SECONDARY_CONFIG="-c ~/.koji/arm-config" build
-</pre>
-To kick off a koji scratch build, run:
+The best place to get help with ARM issues is on #fedora-arm on [https://libera.chat Libera]. The Fedora users and developers from around the world will assist when they are available but due to the many time zones, your question may not be answered right away so its best to remain in the channel. You can also email the Fedora ARM mailing list for assistance.
-<pre>
-koji -c ~/.koji/arm-config build --scratch dist-f13 /path/to/srpm
-</pre>
-You can change the dist tag to the dist you want to target.
-There is also a separate [http://arm.koji.fedoraproject.org/koji/ Fedora ARM Koji Webinterface].
+[[Category:AArch64]]
--->
 [[Category:Arch-specific SIGs]][[Category:SIGs]]
 [[Category:Fedora special-interest groups|ARM]]

Search

Architectures/ARM: Difference between revisions