Difference between revisions of "Generate an RPM-based Raspberry Pi Kernel"
(→Project Plan) |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
== Project Leader(s) == | == Project Leader(s) == | ||
| − | Aries Alwi | + | [[User:asalwi|Aries Alwi]] |
<!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. --> | <!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. --> | ||
| Line 33: | Line 33: | ||
Key contacts: | Key contacts: | ||
| + | * The CDOT Fedora-ARM team: Jordan, Jon, Max, Paul | ||
| + | * Dennis Gilmore | ||
| + | * Dave Jones | ||
<!-- Add links to any mentors or key participants in the community. --> | <!-- Add links to any mentors or key participants in the community. --> | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
| − | * 0.1 | + | * 0.1 Proof of concept : Get the Raspberry Pi packages into the SRPM, modify the spec file to produce a binary RPM for Raspberry Pi. |
| − | * 0.2 | + | * 0.2 Initial implementation : Ensure the post-installation script (%post) in the binary RPM calls grubby properly for the Raspberry Pi. |
| − | * 0.3 | + | * 0.3 Better implementation : Specify the kernel build's configuration file (.config) for what should be included or excluded in terms of device drivers and kernel features. |
== Communication == | == Communication == | ||
=== Mailing Lists === | === Mailing Lists === | ||
| + | * [https://lists.fedoraproject.org/mailman/listinfo/arm arm] | ||
| + | * [https://lists.fedoraproject.org/mailman/listinfo/announce announce] | ||
| + | * [https://lists.fedoraproject.org/mailman/listinfo/devel devel] | ||
| + | * [https://lists.fedoraproject.org/mailman/listinfo/secondary secondary] | ||
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | <!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | ||
| Line 50: | Line 57: | ||
=== Links/Bugs/Tracking === | === Links/Bugs/Tracking === | ||
| + | Building a custom kernel: | ||
| + | * http://fedoraproject.org/wiki/Building_a_custom_kernel | ||
| + | * http://www.howtoforge.com/kernel_compilation_fedora | ||
| + | |||
| + | Dracut: http://fedoraproject.org/wiki/Dracut | ||
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | <!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | ||
=== Source Code Control === | === Source Code Control === | ||
| + | github (Raspberry Pi): https://github.com/raspberrypi/linux | ||
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories --> | <!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories --> | ||
| Line 59: | Line 72: | ||
<!-- Links to the blogs of people involved, both inside and outside Seneca --> | <!-- Links to the blogs of people involved, both inside and outside Seneca --> | ||
| − | ==== Seneca | + | ==== Seneca Participants ==== |
| − | + | [[User:asalwi|Aries Alwi]] | |
==== Non-Seneca Participants ==== | ==== Non-Seneca Participants ==== | ||
<!-- Links to the blogs of any non-Seneca participants in this project --> | <!-- Links to the blogs of any non-Seneca participants in this project --> | ||
Latest revision as of 21:34, 12 March 2012
Contents
Generate an RPM-based Raspberry Pi Kernel
Project Description
The Fedora project has a standard RPM kernel package. The Fedora ARM project has extended this package to build separate kernels for various ARM system-on-a-chip (SOC) platforms, generating binary RPM packages for kernel-omap, kernel-tegra, kernel-kirkwood, and so forth. This package should be extended to generate a kernel package for the Broadcom SOC used in the Raspberry Pi (either kernel-raspi or kernel-bcm).
In order to create a standard RPM package file, Dracut (initramfs) will need to be properly supported.
Expected outcome: the Fedora kernel package generates a Raspberry Pi kernel binary RPM.
Skills required: packaging, kernel building
Maximum number of participants: 2 (kernel package, initramfs/dracut setup)
Project Leader(s)
Project Contributor(s)
Project Details
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
- The CDOT Fedora-ARM team: Jordan, Jon, Max, Paul
- Dennis Gilmore
- Dave Jones
Goals for each release and plans for reaching those goals:
- 0.1 Proof of concept : Get the Raspberry Pi packages into the SRPM, modify the spec file to produce a binary RPM for Raspberry Pi.
- 0.2 Initial implementation : Ensure the post-installation script (%post) in the binary RPM calls grubby properly for the Raspberry Pi.
- 0.3 Better implementation : Specify the kernel build's configuration file (.config) for what should be included or excluded in terms of device drivers and kernel features.
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Building a custom kernel:
- http://fedoraproject.org/wiki/Building_a_custom_kernel
- http://www.howtoforge.com/kernel_compilation_fedora
Dracut: http://fedoraproject.org/wiki/Dracut
Source Code Control
github (Raspberry Pi): https://github.com/raspberrypi/linux
Blogs
http://asalwi123.wordpress.com/
