Difference between revisions of "Package the Raspberry Pi kernel utility"

From CDOT Wiki
Jump to: navigation, search
(Kernel Utility Package Releases)
(Blogs)
 
(2 intermediate revisions by the same user not shown)
Line 31: Line 31:
  
 
[http://matrix.senecac.on.ca/~nhnguyen3/SBR600/Release03/update/raspi-tools.spec SPEC File]
 
[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. -->
  
Line 64: 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://namsbloging.blogspot.ca/ Nam Nguyen's SBR600 Blog]
+
[http://sharethecode.blogspot.ca// http://sharethecode.blogspot.ca/]
 
==== Seneca Particpants ====
 
==== Seneca Particpants ====
Nam Nguyen
+
Joseph Nam Nguyen
  
 
==== Non-Seneca Participants ====
 
==== Non-Seneca Participants ====

Latest revision as of 23:55, 22 January 2016

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

Release 0.1

Release 0.2

Release 0.3

SPEC File

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

Non-Seneca Participants

Planets

Planet CDOT

Project News