View source for Kernel Configuration Files

= Kernel Configuration Files =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->

== Project Description ==

Optimizing Pidora's Kernel Configuration Files for the Raspberry Pi

== Project Leader ==

[http://zenit.senecac.on.ca/wiki/index.php/User:Jason_Michael_Carman Jason Carman]

== Project Contributor(s) ==

<!-- Name(s) of people casually working on the project, or who have contributed significant help.  Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.

NOTE: only the Project Leader should add names here.  You should not add your own name to the Contributor list. -->

== Project Details ==

<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->

The build process for the kernel uses a configuration file to control which kernel capabilities are built into the kernel itself, which are built as loadable modules, and which are not built. This project involves reviewing the Pidora kernel configuration to optimize it for the widest possible range of use-cases while ensuring a fairly small kernel image size.
== Project Plan ==

=== Tracking ===
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->

=== Key contacts ===
<!-- Add links to any mentors or key participants in the community. -->
Andrew Green
=== Goals by Release ===

Goals for each release and plans for reaching those goals:
<!-- Note: Each student must 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 - Initial packaging and extensive testing. Optimized kernel package sent for review in Pidora.
* 0.2 - Review issues addressed, package through the review process.
* 0.3 - Package in Pidora.

== Communication ==
=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
[https://lists.fedoraproject.org/mailman/listinfo/kernel Fedora Project Kernel]
=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->

=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->

=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
[https://github.com/jmcarman/linux github]

=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
[http://jasoncarman.wordpress.com Jason's Blog]

=== Non-Seneca Participants ===
<!-- Links to the blogs of any non-Seneca participants in this project -->

=== Planets ===
<!-- Links to any planets related to this project -->
[http://zenit.senecac.on.ca/~chris.tyler/planet/ CDOT Planet]

== Project News ==

<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->
2013-10-08: Began Project