(→Fedora ARM Remixes)
|Line 12:||Line 12:|
For a list of all supported boards and full installation instructions see the [http://scotland.proximity.on.ca/contrib-images/hansg/README README].
For a list of all supported boards and full installation instructions see the [http://scotland.proximity.on.ca/contrib-images/hansg/READMEREADME].
=== Cubieboard ===
=== Cubieboard ===
Revision as of 07:18, 7 August 2013
Fedora 18 for ARM Remixes
Some ARM devices are not officially supported by Fedora because of proprietary drivers and firmware that do not meet the Fedora guidelines. Below includes a list of devices and links to unsupported Fedora Remixes.
The Raspberry Pi is supported by work done at Seneca College in Toronto, Canada. You can find more information by visiting their site, including links to current release images
Hans de Goede has released an Allwinner A10 remix supporting a variety of devices including the Gooseberry development board, Mele, Mini-X, mk802 and mk802ii and more. It can be downloaded from:
For a list of all supported boards and full installation instructions see the README.
Samsung Exynos 5 Dual Core Cortex A15
There is not currently a finished remix for this device, but very alpha instructions for building your own are available at Architectures/ARM/Samsung_Chromebook_2012. You might also try Darryl Pierce's instructions on his blog. Finally, Daniel P Berrangé has posted an installation script on his blog
There is not currently a finished remix for this device, Rob Clark's instructions for building your own are available at https://github.com/freedreno/touchpad-fedora.
Genesi Efika MX Smartbook
There is work being done on getting the Genesi Smartbook to function nicely with a recent Fedora release. The Smartbook has a Freescale i.MX515 (ARM Cortex-A8 800MHz) SOC with 512MB RAM. Go to the Fedora ARM Genesi Smartbook page for the current status of the hardware support and installation instructions.
Creating your own Remix
Anybody can create a remix of Fedora 18 for their ARM device. Generally all that is needed is an appropriate kernel for the hardware in question. See Architectures/ARM/Installer for an introduction into building images based on a kickstart file. You can also download a tarball of a generic root filesystem for use with your own custom kernel: