From Fedora Project Wiki

< Changes

Revision as of 22:15, 2 July 2013 by Ausil (talk | contribs) (Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


ARM as primary Architecture

Summary

Make ARM a primary architecture. add armv7hl to the i686 and x86_64 as arches that we build every package for. This will mean that all packages must build for ARM to be released. As of Fedora 19 we have dropped support for software floating support so we are only talking about adding hardware floating point 32 bit support.

Owner

Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-07-02
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Enables fedora to embrace the emerging arm world. There is currently servers and desktop like systems that can be used to run Fedora on. ARM systems use very little power, the OLPC XO 1.75 and newer devices are all arm based.

Scope

Add armv7hl to list of arches for f20-build and future build tags in koji compose armhfp trees with i386 and x86_64 Build hardware already exists in phx2 and is configured to talk to koji.

  • Proposal owners:
  • Other developers: submit builds as normal, in the event of unexpected build failures talk to the arm team to help debug and fix issues
  • Release engineering: Releng will need to add armhfp to the release processes and make arm install trees and disk images with each milestone compose
  • Policies and guidelines: armv7hl builds will be required to complete for builds to be successful in koji

Upgrade/compatibility impact

systems running Fedora 18 or 19 should be upgradeable in the same way as x86 systems are.


How To Test

there are many different test vectors, most visible to developers will be that when they submit a build a armv7hl build happens also.

User Experience

User experience really does not change. the difference will be the path in which they use to download files from on the mirrors.

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) If for some reason
  • Contingency deadline:
  • Blocks release? Yes

Documentation

Release Notes