1,885
edits
Changes
Created page with '= Headless IP Address Communication = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == The Raspberry Pi (and som…'
= Headless IP Address Communication =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
The Raspberry Pi (and some other development boards) may be run "headless" in certain applications - without a monitor connected. However, to connect over ethernet for remote diagnostics, it is necessary to know the IP address of the system. This project involves communicating the address through other available means, such as the LED or audio system.
<!-- 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) ==
[[User:Chris Tyler|Chris Tyler]]
<!-- 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) ==
''None so far!''
<!-- 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 ==
The two most obvious ways to provide IP address information are:
(1) to flash the programmable LED on the Pi (or other development board) and
(2) to "read" the IP address over the audio system
This project involves:
* creating scripts to do both of these
* creating the appropriate systemd service files so that the scripts can be run at boot time
* packaging all of this up for inclusion in Fedora
<!-- 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 ==
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
<!-- Add links to any mentors or key participants in the community. -->
* ''Fedora-ARM 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
** Scripts written and tested
** First draft of the systemd service files
** First draft of the RPM package
* 0.2
** Service files tested
** Package finalized
** Package in review
* 0.3
** Package review successfully completed
== Communication ==
=== Mailing Lists ===
* [http://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org]
<!-- 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 ====
* [http://blog.chris.tylers.info Chris Tyler]
==== Non-Seneca Participants ====
* ''None yet''
<!-- 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. -->
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
The Raspberry Pi (and some other development boards) may be run "headless" in certain applications - without a monitor connected. However, to connect over ethernet for remote diagnostics, it is necessary to know the IP address of the system. This project involves communicating the address through other available means, such as the LED or audio system.
<!-- 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) ==
[[User:Chris Tyler|Chris Tyler]]
<!-- 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) ==
''None so far!''
<!-- 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 ==
The two most obvious ways to provide IP address information are:
(1) to flash the programmable LED on the Pi (or other development board) and
(2) to "read" the IP address over the audio system
This project involves:
* creating scripts to do both of these
* creating the appropriate systemd service files so that the scripts can be run at boot time
* packaging all of this up for inclusion in Fedora
<!-- 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 ==
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
<!-- Add links to any mentors or key participants in the community. -->
* ''Fedora-ARM 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
** Scripts written and tested
** First draft of the systemd service files
** First draft of the RPM package
* 0.2
** Service files tested
** Package finalized
** Package in review
* 0.3
** Package review successfully completed
== Communication ==
=== Mailing Lists ===
* [http://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org]
<!-- 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 ====
* [http://blog.chris.tylers.info Chris Tyler]
==== Non-Seneca Participants ====
* ''None yet''
<!-- 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. -->
