Changes

Jump to: navigation, search

Raspberry Pi Fedora Remix FAQ

188 bytes removed, 13:45, 20 September 2012
Developers needed
== What's in the Remix? ==
The Remix package set was selected to provide a good selection of packages for both graphical and non-graphical operation, while providing a manageable download size and installing onto a 2GB SD card. Here are some highlights of the applications includedin RPFR14:
* Desktop GUI environments
== What are the Future Plans for the Raspberry Pi Fedora Remix? ==
The future of the Remix is closely tied to the plans of the [[:fedora:Architecture/ARM|Fedora ARM]] project. The next major release of Fedora ARM will be [[:fedora:Releases/17|Fedora 17]]. It is intended that the Fedora ARM 17 release will be made concurrently with, or very close to, the release of Fedora 17 for primary architectures (x86 32- and 64-bit PCs) in May 2012. By the release of Fedora 19 20 in May November 2013, the ARM architecture will hopefully be promoted to [[:fedora:Architectures|Primary Architecture]] status, meaning that the ARM release will be done in lock-step with the x86 PC release.
A group of students in the Seneca [[SBR600]] class ([[Winter 2012 SBR600 Participants|Winter 2012]]) has worked to polish the Remix for the F17/F18 releases. This work is being carried forward by the Fedora-ARM research group at Seneca. The RPFR17 test images are currently available, with a final release expected in October 2012. A further-optimized RPFR18 release is planned for December 2012.
The number of packages in the Raspberry Pi-specific repositories is expected to diminish over time -- by the time that Fedora 18 19 is released (November May 2012), the Raspberry Pi repositories should hopefully contain mot much more than the VideoCore libraries and headers. (If these were ever to become licensed these under an [http://opensource.org OSI]-approved license then the need for a Remix will be eliminated, and the Raspberry Pi could be directly supported as a Fedora target).
== Can I Remix the Remix? ==
There is one area that stands out as needing particular attention: making the multimedia capabilities of the Raspberry Pi accessible through standard interfaces, particularly:
* audio (on HDMI and analog outputs) via PulseAudio/ALSA
* GPU access via X11 (accelerated X)
* OpenGL via glx

Navigation menu