Difference between revisions of "General HW enablement"
| Line 24: | Line 24: | ||
<!-- 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) == | ||
| + | |||
Here are some Trim-Slice Projects in motion: [http://www.trimslice.com/wiki/index.php/Trim-Slice_Projects Trim-Slice Projects]<br /><br /> | Here are some Trim-Slice Projects in motion: [http://www.trimslice.com/wiki/index.php/Trim-Slice_Projects Trim-Slice Projects]<br /><br /> | ||
| Line 46: | Line 47: | ||
== Project Plan == | == Project Plan == | ||
| − | + | 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. --> | <!-- 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. --> | ||
* <u>0.1 - '''Design:'''</u> Designing a rough version of our package within a fedora platform.<br /><br /> | * <u>0.1 - '''Design:'''</u> Designing a rough version of our package within a fedora platform.<br /><br /> | ||
| Line 63: | Line 64: | ||
=== Mailing Lists === | === 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.<br /><br /> | 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 /> | ||
Revision as of 16:56, 30 October 2012
Contents
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:
- Trim-Slice (Official Website): Trim-Slice
- Trim-Slice HW Details: Trim-Slice Specs
- Trim-Slice Features: Trim-Slice Features
- Trim-Slice Linux: Trim-Slice Linux
- Trim-Slice Articles: Trim-Slice Articles
- Check out other projects within SBR-600: Other Projects
Project Leaders
- Nikhil Sharma:
- Learn a little about Nikhil here: About Nikhil
- Check out Nikhil's blog here: Nikhil's Blog
- Hugo Pombo:
- Learn a little about Hugo here: About Hugo
- Check out Hugo's blog here: Hugo's Blog
- Learn a little about Hugo here: About Hugo
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:
- 0.1 - Design: Designing a rough version of our package within a fedora platform.
- 0.2 - Finalize: Finalizing our package to a qualified level, followed by a submission to the Fedora Packaging Review Committee.
- 0.3 - Presentation: Prepare our approved fedora package for the project presentation.
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:
- Take advantage of tracking mechanisms such as: bugzilla, trac, github, etc.
- 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
Upsteam Wiki and Web
Coming Soon...
