No edit summary |
(review doc) |
||
| Line 10: | Line 10: | ||
= Introduction = | = Introduction = | ||
Welcome to the architecture page for ARM. This covers both ARMv7 (aka armhfp and arm-32) and aarch64 (aka ARMv8 and arm-64). | Welcome to the architecture page for an 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 | 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 use cases 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 | 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 == | == Getting started == | ||
The first starting point for ARM is the [[Architectures/ARM/Installation | ARM Installation Guide]] . | The first starting point for ARM is the [[Architectures/ARM/Installation | ARM Installation Guide]]. | ||
== Download == | == Download == | ||
| Line 69: | Line 69: | ||
=== Scratch an itch === | === Scratch an itch === | ||
All architectures are now integrated into the standard Fedora process. We don't diverge in any way. So without even | 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 === | === 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 [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]. | 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]. | ||
=== Getting help with ARM build issues === | === 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. | 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 the channel. You can also email the Fedora ARM mailing list for assistance. | ||
[[Category:ARMv7]][[Category:AArch64]] | [[Category:ARMv7]][[Category:AArch64]] | ||
[[Category:Arch-specific SIGs]][[Category:SIGs]] | [[Category:Arch-specific SIGs]][[Category:SIGs]] | ||
[[Category:Fedora special-interest groups|ARM]] | [[Category:Fedora special-interest groups|ARM]] | ||
Revision as of 19:05, 8 August 2018
 |
Introduction
Welcome to the architecture page for an 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 use cases 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 release
The development release is Fedora 29 (Rawhide):
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
- Chromebooks
- SBSA aarch64 Servers
- 96Boards devices
- All Winner based devices
- Marvell EBU based devices
- nVidia Tegra based devices
- NXP i.MX6 based devices
- RockChips based devices
- STMicroelectronics based devices
- Samsung EXYNOS based devices e.g., Odroid XU4
- 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.
Supported Hardware Addons
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 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 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 the channel. You can also email the Fedora ARM mailing list for assistance.