Difference between revisions of "Package the Raspberry Pi kernel utility"
(→Project Name) |
(→Blogs) |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 23: | Line 23: | ||
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. --> | NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. --> | ||
| − | == | + | == Kernel Utility Package Releases == |
| + | [http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release01/ Release 0.1] | ||
| + | [http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release02/ Release 0.2] | ||
| + | |||
| + | [http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release03/update/ Release 0.3] | ||
| + | |||
| + | [http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release03/update/raspi-tools.spec SPEC File] | ||
<!-- 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. --> | <!-- 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. --> | ||
== Project Plan == | == Project Plan == | ||
| − | Tracking mechanism | + | Tracking mechanism : github |
| − | Key contacts: | + | Key contacts: ctyler |
<!-- 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 Proof of concept - Research | + | * 0.1 Proof of concept - Research and obtain the file that is used as the Raspberry Pi Kernel utility. Successfully Package the file using rpmbuild into an SRPM & RPM |
| − | * 0.2 Initial working state - | + | * 0.2 Initial working state - Test the RPM for errors with rpmlint, mock, koji. Attempt to have errors resolved and then have package reviewed by the community |
| − | * 0.3 Completed working state - | + | * 0.3 Completed working state - Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package. |
== Communication == | == Communication == | ||
| Line 46: | Line 52: | ||
=== Upsteam Wiki and Web === | === Upsteam Wiki and Web === | ||
| + | [http://www.github.com/raspberrypi/tools/tree/master/mkimage https://github.com/raspberrypi/tools/tree/master/mkimage] | ||
<!-- Links to upstream wiki/web pages --> | <!-- Links to upstream wiki/web pages --> | ||
| Line 56: | Line 63: | ||
=== Blogs === | === Blogs === | ||
<!-- Links to the blogs of people involved, both inside and outside Seneca --> | <!-- Links to the blogs of people involved, both inside and outside Seneca --> | ||
| − | + | [http://sharethecode.blogspot.ca// http://sharethecode.blogspot.ca/] | |
==== Seneca Particpants ==== | ==== Seneca Particpants ==== | ||
| − | Nam Nguyen | + | Joseph Nam Nguyen |
==== Non-Seneca Participants ==== | ==== Non-Seneca Participants ==== | ||
| Line 64: | Line 71: | ||
==== Planets ==== | ==== Planets ==== | ||
| + | [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT] | ||
<!-- Links to any planets related to this project --> | <!-- Links to any planets related to this project --> | ||
Latest revision as of 22:55, 22 January 2016
Contents
Package the Raspberry Pi Kernel Utility
Project Description
The Raspi bootloader requires a special header at the start of the kernel file in order to correctly load it into memory. The tool which creates this header needs to be packaged in Fedora.
Expected outcome: a Fedora package for the Raspberry Pi kernel utility.
Skills required: packaging
Project Leader(s)
Nam Nguyen
Project Contributor(s)
Kernel Utility Package Releases
Project Plan
Tracking mechanism : github
Key contacts: ctyler
Goals for each release and plans for reaching those goals:
- 0.1 Proof of concept - Research and obtain the file that is used as the Raspberry Pi Kernel utility. Successfully Package the file using rpmbuild into an SRPM & RPM
- 0.2 Initial working state - Test the RPM for errors with rpmlint, mock, koji. Attempt to have errors resolved and then have package reviewed by the community
- 0.3 Completed working state - Fix any remaining errors with package and complete Readme files and documentation. Have a finished and working kernel utility package.
Communication
Mailing Lists
Upsteam Wiki and Web
https://github.com/raspberrypi/tools/tree/master/mkimage
Links/Bugs/Tracking
Source Code Control
Blogs
http://sharethecode.blogspot.ca/
Seneca Particpants
Joseph Nam Nguyen
