Difference between revisions of "RPM-based Kernels for Fedora ARM"

From CDOT Wiki
Jump to: navigation, search
Line 22: Line 22:
  
 
== Project Details ==
 
== Project Details ==
 
+
In PCs, when you turn on the machine, the system reads BIOS to locate the MBR which is the first 512 byte of hard disk. Then, the MBR says the location of GRUB and the
 +
GRUB program starts to load kernel. Finally, the kernel loads modules and init scripts to boot system up. IN ARM system, because we do not have any BIOS or Hard disk, the
 +
process is different.
 
<!-- 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. -->
  

Revision as of 21:40, 30 January 2011

RPM-based Kernels for Fedora ARM

Project Description

This project is related to making a RPM for kernels in Fedora ARM. Because of different architecture and hardware compared to PCs, the way that ARM loads kernels and other boot processes is different than PCs. We are going to make a RPM that loads kernels, modules, init, and other boot process in ARM system in standard way like PCs and try to bind these packages together.


Project Leader(s)

Chris Tyler

Project Contributor(s)

Khosro Taraghi

Project Details

In PCs, when you turn on the machine, the system reads BIOS to locate the MBR which is the first 512 byte of hard disk. Then, the MBR says the location of GRUB and the GRUB program starts to load kernel. Finally, the kernel loads modules and init scripts to boot system up. IN ARM system, because we do not have any BIOS or Hard disk, the process is different.

Project Plan

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:

Goals for each release and plans for reaching those goals:

  • 0.1
  • 0.2
  • 0.3

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Seneca Particpants

Non-Seneca Participants

Planets

Project News