Revision as of 14:59, 30 November 2017

Shortcut: Arch:ARM

Shortcut: Arch:AArch64

Have a question?
Join the Fedora ARM team on IRC in #fedora-arm on Freenode

Introduction

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.

Getting started

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

Download

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:

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.

Supported Hardware Addons

i2c and devices attached to i2c

Get Involved with Fedora ARM

Communication

Mailing list: arm (archives)
IRC: #fedora-arm^[?] on http://freenode.net

Meetings

IRC: #fedora-meeting-2^[?] 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.

Bug Reporting

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.

Getting help with ARM build issues

The best place to get help with ARM issues is on #fedora-arm on Freenode. 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 channel. You can also email the Fedora ARM mailing list for assistance.

@@ Line 1: / Line 1: @@
-{{Draft}}{{Admon/note|Refactoring|This portion of the wiki is currently being refactored.}}
+{{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 [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]
+}}
+|}
 = Introduction =
-= Resources =
-* [[Architectures/ARM/Team and Developers]]
-* [[Architectures/ARM/Using]]
-* [[Architectures/ARM/Package Maintainers]]
-----
+Welcome to the architecture page for ARM. This covers both ARMv7 (aka armhfp and arm-32) and aarch64 (aka ARMv8 and arm-64).
-'''OLD PAGE CONTENTS HERE'''
+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.
-<!-- page was renamed from ARM -->
-= Fedora ARM =
+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.
-This is the starting page for the Fedora port to the ARM architecture.
+== Getting started ==
+The first starting point for ARM is the [[Architectures/ARM/Installation | ARM Installation Guide]].
+== Download ==
-== Goals and Objectives ==
+=== Current stable release ===
-The primary goal of this project is to provide support for ARM as a [[TomCallaway/SecondaryArchitectures|  secondary architecture]]  in Fedora.
+The current stable release for ARMv7 can always be found at the [https://arm.fedoraproject.org/ ARM Image landing page]
-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.
+The current stable release for aarch64 can always be found at [https://alt.fedoraproject.org/alt/ Alternate Architectures landing page]
-== Technical Approach ==
+=== Current development releases ===
-=== Native Compilation ===
+There are currently two development releases. Fedora 26 is in the stabilisation phase, Fedora rawhide (27) is in the development phase.
-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.
+== Supported Hardware and Devices ==
-=== CPU and Architecture Target ===
+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.
-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.
+Here is list of device pages based on device category or SoC:
-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.
+* [[Architectures/ARM/Raspberry_Pi|Raspberry Pi]]
+* [[Architectures/ARM/Chromebook|Chromebooks]]
+* [http://docs.fedoraproject.org/en-US/Fedora/26/html/Installation_Guide/chap-pxe-server-setup.html SBSA aarch64 Servers]
+* [[Architectures/ARM/96Boards|96Boards devices]]
+* [[Architectures/ARM/AllWinner|All Winner based devices]]
+* [[Architectures/ARM/mvebu|Marvell EBU based devices]]
+* [[Architectures/ARM/Tegra|nVidia Tegra based devices]]
+* [[Architectures/ARM/iMX6|NXP i.MX6 based devices]]
+* [[Architectures/ARM/RockChips|RockChips based devices]]
+* [[Architectures/ARM/STi|STMicroelectronics based devices]]
+* [[Architectures/ARM/exynos|Samsung EXYNOS based devices]] e.g., Odroid XU4
+* [[Architectures/ARM/TI|Texas Instruments based devices]]
-=== Installer and Kernel ===
+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.
-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.
+= Supported Hardware Addons =
+* [[Architectures/ARM/i2c|i2c and devices attached to i2c]]
-== Contribute ==
+= Get Involved with Fedora ARM =
-* 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? ===
+=== Communication ===
-* The [https://admin.fedoraproject.org/mailman/listinfo/arm Fedora-ARM mailing list]  is available for both user and developer discussions.
-* 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 ===
+* Mailing list: {{fplist|arm}} ([https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/ archives])
-If excluding ARM architectures you need to make the bug block '''F-ExcludeArch-ARM'''
+* IRC: {{fpchat|#fedora-arm}} on http://freenode.net
-to see whats currently blocking visit [https://bugzilla.redhat.com/show_bug.cgi?id=F-ExcludeArch-ARM  Bugzilla ]
+=== Meetings ===
+* IRC: {{fpchat|#fedora-meeting-2}} Every Tuesday at 16:00 UTC.
-If a bug is specific to ARM architectures make the bug blocking '''ARMTracker'''
+=== 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.
-to see not yet resolved issues visit [https://bugzilla.redhat.com/show_bug.cgi?id=ARMTracker  Bugzilla ]
+=== Bug Reporting ===
-=== Package Maintainer Notes ===
+Bugs should be reported against their prospective packages as per 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].
-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:
+=== Getting help with ARM build issues ===
-<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].
+The best place to get help with ARM issues is on #fedora-arm on Freenode. 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 channel. You can also email the Fedora ARM mailing list for assistance.
+[[Category:ARMv7]][[Category:AArch64]]
 [[Category:Arch-specific SIGs]][[Category:SIGs]]
 [[Category:Fedora special-interest groups|ARM]]

Search

Architectures/ARM: Difference between revisions