Difference between revisions of "General HW enablement"

From CDOT Wiki
Jump to: navigation, search
(→‎Project News)
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
= General Hardware Enablement: FM Radio/GPS =
+
= General Hardware Enablement of WiFi & Bluetooth Using Trim Slice =
−
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
  
 
== Project Description ==
 
== Project Description ==
  
−
A number of ARM boards have features that are not fully supported in Fedora.
+
Most of the devices fedora supports actually only use a small amount of the hardware that is on the device. Whether it is something simple like graphics and sound or more complex features such as GYRO, GPS, FM Radio, WiFi, Bluetooth, etc. There's also some other devices that would be interesting to support like the Snowball, Origen, or even the Vivaldi Tablet. Some definitely need FW and hence probably packaging if it's not in the linux-firmware dumping ground.  Having considered all of this information, it is our intention to enable WiFi & Bluetooth on the Trim Slice board using Fedora 17 as our platform.<br /><br />
−
 
 
−
Note: Before starting this project, you must identify the features and boards you are targeting.
 
−
 
 
−
From Peter Robinson:
 
−
 
 
−
Most of the devices we support actually only use a small amount of the HW that is actually on the device. Whether it be simple like graphics or sound or more interesting like gyro, gps, FM radio. There's also some other devices that would be interesting to support like the snowball, origen, or even the Vivaldi Tablet. Some definitely need FW and hence probably packaging if it's not in the linux-firmware dumping ground
 
−
 
 
−
Expected outcome: The identified features will be supported on the identified board(s) within Fedora.
 
  
 +
<u>Relevant On-Line Resources:</u><br />
 +
#''Trim-Slice (Official Website):'' [http://trimslice.com/web/ Trim-Slice]
 +
#''Trim-Slice HW Details:'' [http://en.wikipedia.org/wiki/Trim-Slice Trim-Slice Specs]
 +
#''Trim-Slice Features:'' [http://trimslice.com/web/trim-slice-features Trim-Slice Features]
 +
#''Trim-Slice Linux:'' [http://www.trimslice.com/wiki/index.php/Trim-Slice_Linux Trim-Slice Linux]
 +
#''Trim-Slice Articles:'' [http://www.engadget.com/tag/Trim+Slice/ Trim-Slice Articles]
 +
#''Check out other projects within SBR-600:'' [http://zenit.senecac.on.ca/wiki/index.php/Fall_2012_DPI908/SBR600_Participants Other Projects]<br /><br />
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 +
== Project Leaders ==
  
−
== Project Leader(s) ==
+
*<u>'''Nikhil Sharma:'''</u><br />
 +
**Learn a little about Nikhil here: [http://zenit.senecac.on.ca/wiki/index.php/User:Nikhil_Shrey_Sharma About Nikhil]
 +
**Check out Nikhil's blog here: [http://i0x777.wordpress.com Nikhil's Blog]<br /><br />
  
−
Nikhil Sharma
+
*<u>'''Hugo Pombo:'''</u><br />
−
Wiki: [http://zenit.senecac.on.ca/wiki/index.php/User:Nikhil_Shrey_Sharma]
+
**Learn a little about Hugo here: [http://zenit.senecac.on.ca/wiki/index.php/User:hapombo About Hugo] <br />
−
Blog: [http://www.elite-mafia.net/blog Blog]
+
**Check out Hugo's blog here: [http://hapombo.blogspot.ca/ Hugo's Blog]<br /><br />
−
 
 
−
Hugo Pombo: WIKI : BLOG
 
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
  
 
== Project Contributor(s) ==
 
== 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.
+
Here are some Trim-Slice Projects in motion: [http://www.trimslice.com/wiki/index.php/Trim-Slice_Projects Trim-Slice Projects]<br /><br />
  
−
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. -->
+
As you can see, there are many projects being researched, each with their own little community.  We would have liked to thank everyone involved with these projects individually, but there are too many names to mention. One might consider it to be non-practical to list each individual separately (we are talking about hundreds of people involved).
  
 +
Instead, we would like to thank EVERYONE involved with these projects as a whole, as their research is helping us with our project.  It is because of these individuals that the Trim-Slice community thrives.  Keep up the good work everyone!!!<br /><br />
 +
 +
That being said, because our research revolves around Fedora, we would like to send out a special thanks to the individuals who's projects are similar to ours:
 +
*lesliew (Forum Author)
 +
*HenrikN (Forum Author)<br /><br />
 +
<!-- 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 Project Leader(s) should add names here.  You should not add your own name to the Contributor list. -->
 
== Project Details ==
 
== 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. -->
+
*<u>Expected outcome:</u> The identified features will be supported on the identified board(s) within Fedora.
−
 
 
−
== Project Plan ==
 
−
 
 
−
Tracking mechanism (bugzilla, trac, github, ...):
 
  
−
Key contacts:
+
*<u>Skills required:</u> packaging, kernel/module building, testing
−
Chris Tyler (ctyler), Peter Robinson (pbrobinson)
 
  
−
Goals for each release and plans for reaching those goals:
+
*<u>Maximum number of students:</u> One per hardware feature to be supported
−
<!-- 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
 
−
* 0.2
 
−
* 0.3
 
−
 
 
−
== Communication ==
 
−
 
 
−
=== Mailing Lists ===
 
−
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
 
−
 
 
−
=== 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 -->
 
−
 
 
−
=== Blogs ===
 
−
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
−
 
 
−
==== Seneca Particpants ====
 
−
 
 
−
==== Non-Seneca Participants ====
 
−
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
−
 
 
−
==== Planets ====
 
−
<!-- Links to any planets related to this project -->
 
−
 
 
−
== 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. -->
 
−
 
 
−
 
 
−
 
 
−
===============================================================================================================================================================
 
−
 
 
−
= Project Name =
 
−
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
−
 
 
−
== Project Description ==
 
−
 
 
−
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
−
 
 
−
== Project Leader(s) ==
 
−
 
 
−
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
 
−
 
 
−
== 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 Project Leader(s) should add names here.  You should not add your own name to the Contributor list. -->
 
−
 
 
−
== Project Details ==
 
  
 +
*<u>Resources:</u> Chris Tyler (ctyler), Peter Robinson (pbrobinson)<br /><br />
 
<!-- 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 (bugzilla, trac, github, ...):
+
Here are our goals for each release and plans for reaching those goals:<br /><br />
 +
<!-- 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. -->
 +
(Discontinued)
 +
* <u>0.1 - '''Design:'''</u> Designing a rough version of our package within a fedora platform.<br /><br />
  
−
Key contacts:
+
(Revised)
−
<!-- Add links to any mentors or key participants in the community. -->
+
* <u>0.2 - '''Draft Edition:'''</u>  Test Bluetooth/WiFi on the Trim Slice, create a draft version of a Test Plan along with a draft version of a Script (to automate the process).<br /><br />
  
−
Goals for each release and plans for reaching those goals:
+
* <u>0.3 - '''Final Edition:'''</u>  Create a final version of our Test Plan and finalize our Scripts for optimal efficiency.  Resulting with the end user acquiring success when using Bluetooth/WiFi technology with the Trim-Slice Pro.<br /><br />
−
<!-- 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
 
−
* 0.2
 
−
* 0.3
 
  
 +
<u>'''IMPORTANT:'''</u><br />
 +
I Hugo Pombo and Nikhil Sharma will be implementing each section of our project plan <u>individually</u>.<br /><br />
 +
Here is the declared ownership of hardware we are aspiring to enable:<br />
 +
*<u>Hugo Pombo:</u> Enabling Bluetooth on the Trim-Slice board.<br /><br />
 +
*<u>Nikhil Sharma:</u> Enabling WiFi on the Trim-Slice board.<br /><br />
 +
<u>'''Notes:'''</u><br />
 +
#Take advantage of tracking mechanisms such as: bugzilla, trac, github, etc.
 +
#Using our key contacts: '''Chris Tyler (ctyler), Peter Robinson (pbrobinson).'''<br /><br />
 
== Communication ==
 
== Communication ==
  
 
=== Mailing Lists ===
 
=== Mailing Lists ===
−
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
 
  
−
=== Upsteam Wiki and Web ===
+
We are currently attempting to find a new and appropriate mailing list of which to subscribe to.  However there does not seem to be a specific mailing list that revolves around Trim-Slice projects.  We will attempt to find a more generic mailing list that can be of some assistance to this project.  Once found, we will let you know and update this section.<br /><br />
−
<!-- Links to upstream wiki/web pages -->
 
  
−
=== Links/Bugs/Tracking ===
+
<u>As of now, we are currently subscribed to these mailing lists:</u>
−
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
+
*secondary-request@lists.fedoraproject.org
 +
*devel-request@lists.fedoraproject.org
 +
*announce-request@lists.fedoraproject.org
 +
*arm-request@lists.fedoraproject.org<br /><br />
  
−
=== Source Code Control ===
+
Here is a link to the mailing lists: [https://lists.fedoraproject.org/mailman/listinfo Mailing Lists]<br /><br />
−
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
+
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
−
 
 
−
=== Blogs ===
 
−
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
  
 
==== Seneca Particpants ====
 
==== Seneca Particpants ====
−
 
+
So far, we are the only known Seneca participants with regards to this project.  Please, periodically check this page for updates.
−
==== Non-Seneca Participants ====
 
−
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
−
 
 
−
==== Planets ====
 
−
<!-- Links to any planets related to this project -->
 
  
 
== Project News ==
 
== Project News ==
−
 
+
Please see our blogs for our final deliverable files.  Thank You.
 
<!-- 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. -->
 
<!-- 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. -->

Latest revision as of 23:44, 8 December 2012

General Hardware Enablement of WiFi & Bluetooth Using Trim Slice

Project Description

Most of the devices fedora supports actually only use a small amount of the hardware that is on the device. Whether it is something simple like graphics and sound or more complex features such as GYRO, GPS, FM Radio, WiFi, Bluetooth, etc. There's also some other devices that would be interesting to support like the Snowball, Origen, or even the Vivaldi Tablet. Some definitely need FW and hence probably packaging if it's not in the linux-firmware dumping ground. Having considered all of this information, it is our intention to enable WiFi & Bluetooth on the Trim Slice board using Fedora 17 as our platform.

Relevant On-Line Resources:

  1. Trim-Slice (Official Website): Trim-Slice
  2. Trim-Slice HW Details: Trim-Slice Specs
  3. Trim-Slice Features: Trim-Slice Features
  4. Trim-Slice Linux: Trim-Slice Linux
  5. Trim-Slice Articles: Trim-Slice Articles
  6. Check out other projects within SBR-600: Other Projects

Project Leaders

Project Contributor(s)

Here are some Trim-Slice Projects in motion: Trim-Slice Projects

As you can see, there are many projects being researched, each with their own little community. We would have liked to thank everyone involved with these projects individually, but there are too many names to mention. One might consider it to be non-practical to list each individual separately (we are talking about hundreds of people involved).

Instead, we would like to thank EVERYONE involved with these projects as a whole, as their research is helping us with our project. It is because of these individuals that the Trim-Slice community thrives. Keep up the good work everyone!!!

That being said, because our research revolves around Fedora, we would like to send out a special thanks to the individuals who's projects are similar to ours:

  • lesliew (Forum Author)
  • HenrikN (Forum Author)

Project Details

  • Expected outcome: The identified features will be supported on the identified board(s) within Fedora.
  • Skills required: packaging, kernel/module building, testing
  • Maximum number of students: One per hardware feature to be supported
  • Resources: Chris Tyler (ctyler), Peter Robinson (pbrobinson)

Project Plan

Here are our goals for each release and plans for reaching those goals:

(Discontinued)

  • 0.1 - Design: Designing a rough version of our package within a fedora platform.

(Revised)

  • 0.2 - Draft Edition: Test Bluetooth/WiFi on the Trim Slice, create a draft version of a Test Plan along with a draft version of a Script (to automate the process).

  • 0.3 - Final Edition: Create a final version of our Test Plan and finalize our Scripts for optimal efficiency. Resulting with the end user acquiring success when using Bluetooth/WiFi technology with the Trim-Slice Pro.

IMPORTANT:
I Hugo Pombo and Nikhil Sharma will be implementing each section of our project plan individually.

Here is the declared ownership of hardware we are aspiring to enable:

  • Hugo Pombo: Enabling Bluetooth on the Trim-Slice board.

  • Nikhil Sharma: Enabling WiFi on the Trim-Slice board.

Notes:

  1. Take advantage of tracking mechanisms such as: bugzilla, trac, github, etc.
  2. Using our key contacts: Chris Tyler (ctyler), Peter Robinson (pbrobinson).

Communication

Mailing Lists

We are currently attempting to find a new and appropriate mailing list of which to subscribe to. However there does not seem to be a specific mailing list that revolves around Trim-Slice projects. We will attempt to find a more generic mailing list that can be of some assistance to this project. Once found, we will let you know and update this section.

As of now, we are currently subscribed to these mailing lists:

  • secondary-request@lists.fedoraproject.org
  • devel-request@lists.fedoraproject.org
  • announce-request@lists.fedoraproject.org
  • arm-request@lists.fedoraproject.org

Here is a link to the mailing lists: Mailing Lists

Seneca Particpants

So far, we are the only known Seneca participants with regards to this project. Please, periodically check this page for updates.

Project News

Please see our blogs for our final deliverable files. Thank You.

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=General_HW_enablement&oldid=91946"