Difference between revisions of "Generate an RPM-based Raspberry Pi Kernel"
(→Links/Bugs/Tracking) |
(→Project Plan) |
||
| Line 40: | Line 40: | ||
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 Proof of concept | + | * 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. | * 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. | ||
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/
