From: Lars-Peter Clausen <lars@metafoo.de>
To: alessandro osima <alex.osima@gmail.com>
Cc: linux-iio@vger.kernel.org, Hunyue Yau <hy-gsoc@hy-research.com>
Subject: Re: Abstracting and extending evdev to work with the iio subsystem
Date: Fri, 03 May 2013 09:50:00 +0200 [thread overview]
Message-ID: <51836C28.4050806@metafoo.de> (raw)
In-Reply-To: <CAOTW74kb_qJP=by_iKOTCHVurh2wEc6nfmdL-F2ddqq3aQ672g@mail.gmail.com>
On 04/30/2013 04:24 AM, alessandro osima wrote:
> Hello everyone, my name is Alessandro Osima and I'm a computer
> science student at Università degli Studi di Milano, Italy (second
> year, equivalent to bachelor).
>
>
> For this year's Google Summer of Code I have decided to submit an
> application proposal focused on abstracting evdev from input to allow
> iio and other subsystems to take advantage of it to send/receive
> events and data to userspace application troughout files located in
> the /dev directory.
>
> This http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/asion/1#
> is my proposal.
>
> I would kindly ask your opinions about this project and would be very
> grateful for any comments and suggestion to improve it.
>
Hi,
Sounds interesting. Did you hd a look at the existing IIO event interface
(drivers/iio/industrialio-event.c)? I'm asking because you don't seem to
mention it in your proposal.
- Lars
next prev parent reply other threads:[~2013-05-03 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 2:24 Abstracting and extending evdev to work with the iio subsystem alessandro osima
2013-05-03 7:50 ` Lars-Peter Clausen [this message]
2013-05-06 22:47 ` Alessandro Osima
2013-05-11 14:18 ` Jonathan Cameron
2013-05-20 1:27 ` Alessandro Osima
2013-05-20 10:37 ` Jonathan Cameron
2013-05-21 23:28 ` Alessandro Osima
2013-05-22 8:06 ` Jonathan Cameron
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=51836C28.4050806@metafoo.de \
--to=lars@metafoo.de \
--cc=alex.osima@gmail.com \
--cc=hy-gsoc@hy-research.com \
--cc=linux-iio@vger.kernel.org \
/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