Changes

Jump to: navigation, search

Add PandaBoards to the Fedora-ARM Build System

91 bytes added, 22:20, 14 March 2011
no edit summary
== Project Plan ==
Tracking mechanism (bugzilla, trac, github, ...)Key contacts: [https://bugzilla.redhat.com/ Bugzilla]
Key contacts:
PaulW and ctyler on the #seneca channel
<!-- Add links to any mentors or key participants in the community. -->
Goals for each release and plans for reaching those goals:
<!-- 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 - Get PandaBoard to see full 1GB of RAM and get Fedora to see it as well.* 0.2 - The kernel blocks off a large amount of RAM for VRAM. Get it to not reserve VRAM anymore.
* 0.3 -
=== Mailing Lists ===
pandaboard@googlegroups.com
 
arm@lists.fedoraproject.org
<!-- 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 -->
[https://perfectlylogical.wordpress.com/Stephen Hall's Blog]
==== Seneca Particpants ====
1
edit

Navigation menu