Difference between revisions of "To Thumb or Not to Thumb"

From CDOT Wiki
Jump to: navigation, search
(Project Contributor(s))
Line 22: Line 22:
  
 
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.
 +
 +
== What I need to learn ==
 +
 +
Pretty much everything from the scratch. It seems like this project requires lots of background information such as RISC, CISC, Instruction set, Register set, different versions of ARM architecture versions, armv5tel and newer ( and better) models and etc.
  
 
== Project Plan ==
 
== Project Plan ==

Revision as of 23:32, 14 October 2010

Project Name

To Thumb? or Not to Thumb?

Project Description

Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, http://google.com or MDC.

Project Leader(s)

I will be working alone for this project. My name is Tae Hee (Tyler) Lee.

thlee3 @ FAS2

thlee3 @ irc://irc.mozilla.org/seneca

Tyler.lee @ Open Source Seneca Wiki

thlee3@learn.senecac.on.ca

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.

What I need to learn

Pretty much everything from the scratch. It seems like this project requires lots of background information such as RISC, CISC, Instruction set, Register set, different versions of ARM architecture versions, armv5tel and newer ( and better) models and etc.

Project Plan

Goals for each release:

  • 0.1
  • 0.2
  • 0.3

Project News

This is where your regular 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.

Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.