From: Shane Morris <edgecomberts@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC '14
Date: Sun, 26 Jan 2014 17:24:49 +1100 [thread overview]
Message-ID: <CANZw+5eh5GMvcMOqmtoCs7xJ8k4m8+oK8iMfyjYZaKdbaNnpwg@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKEF-XjQojABseivgfG1za2j0GnDa9V0uVXAWRMmhMq1fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
Steve, Krystian in Poland has tackled GPIO on the RaspberryPi. I can fish
up his repos if needed...
On Sun, Jan 26, 2014 at 5:22 PM, Steven Stallion <sstallion@gmail.com>wrote:
> On Sat, Jan 25, 2014 at 10:38 PM, Salman Javaid <javaid.salman@gmail.com>
> wrote:
> > Steven, this USB 3 [0] device driver implementation seems to be an
> > interesting project. Is this something you will be interested in?
> >
> > [0] http://www.plan9.bell-labs.com/wiki/plan9/TODO/index.html
>
> That's going to be a bit much to chew off for a student project. USB
> is a non-trivial mess of pain and frustration, even for the
> experienced. If someone is getting started with driver work, the most
> successful path will likely be implementing a simple part (even if
> it's an old one). Ethernet and UARTs come to mind - they tend to be
> the simplest. I think at one point there was a call out to get GPIO
> working on the Raspberry Pi - that would be a good summer project if
> it hasn't been done already. GPIO can be a lot of fun, especially if
> you have a couple of protoboards laying around.
>
> Anyhow, when it comes to GSoC it's far more important to focus on
> attainable goals - it's a lot more fun for the student (and the
> mentor) when something working comes out at the end.
>
> HTH,
>
> Steve
>
>
[-- Attachment #2: Type: text/html, Size: 1866 bytes --]
next prev parent reply other threads:[~2014-01-26 6:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 10:03 Jessica Yu
2014-01-25 15:42 ` Steven Stallion
2014-01-25 22:59 ` Conor Williams
2014-01-26 0:09 ` Anthony Sorace
2014-01-26 1:42 ` Conor Williams
2014-01-26 2:14 ` Steven Stallion
2014-01-26 2:37 ` Conor Williams
2014-01-26 3:37 ` Shane Morris
2014-01-26 4:00 ` Calvin Morrison
2014-01-26 4:04 ` Shane Morris
2014-01-26 4:15 ` erik quanstrom
2014-01-26 4:18 ` Shane Morris
2014-01-26 4:33 ` Steven Stallion
2014-01-26 4:37 ` Shane Morris
2014-01-26 6:25 ` Steven Stallion
2014-01-26 4:38 ` Salman Javaid
2014-01-26 6:22 ` Steven Stallion
2014-01-26 6:24 ` Shane Morris [this message]
2014-01-26 6:28 ` Steven Stallion
2014-01-26 6:30 ` Shane Morris
2014-01-26 14:43 ` erik quanstrom
2014-01-26 16:15 ` Tristan
2014-01-26 19:17 ` Muhammad Junaid Muzammil
2014-01-30 12:16 ` Steve Simon
2014-04-25 11:54 ` Conor Williams
2014-01-26 7:58 ` Jessica Yu
2014-01-26 22:02 ` Steven Stallion
2014-01-27 4:35 ` blstuart
2014-01-27 15:17 ` Jeff Sickel
2014-01-27 16:24 ` Steven Stallion
2014-01-27 17:31 ` Jeff Sickel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANZw+5eh5GMvcMOqmtoCs7xJ8k4m8+oK8iMfyjYZaKdbaNnpwg@mail.gmail.com \
--to=edgecomberts@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).