From: Alison Schofield <amsfield22@gmail.com>
To: linux-iio@vger.kernel.org
Subject: Linux ELC & OpenIoT Report
Date: Sun, 5 Mar 2017 15:52:04 -0800 [thread overview]
Message-ID: <20170305235202.GA6202@d830.WORKGROUP> (raw)
Hi IIO Community,
I attended the Linux Foundation's Embedded Linux and OpenIoT Summit in
Portland, Oregon recently.
I've appended a few excerpts from my blog write-up below and the full
text of my report is available here:
https://outreachyiio.blogspot.com/2017/03/embedded-linux-conference-openiot.html
alisons
2 Things that made me go hmmm:
1) There are developers who believe that user space drivers are more
efficient than kernel drivers. They don't mean more efficient as in they
don't want to bother upstreaming the driver. They actually mean more
efficient in that they think the user space driver performs better. I
didn't meet one of those developers...they were only whispered about ;)
2) Android Things (Intel & Google product) will not use our lovely IIO
drivers. They will not include any non-essential drivers in the kernel
image and there will not be a way to rebuild it. They have set up a git
repository for the world to share user space drivers for sensors.
IIO Community Sightings: Matt Ranostay
Matt gave a great IIO Subsystem presentation!!! It contained a live demo
of one of his more recent driver additions: heart rate and pulse
oximeter. When Matt's hear rate only measured 42, he wrote it off to a
loose connection, but I'm not convinced. I may go look for a bug in that
driver ;)
IIO Community Hindsight: David Lechner
When I met David displaying his ev3 devices at the technical showcase, I
didn't know of him from the IIO community. David has some drivers he
wants upstreamed to IIO. Potential Outreachy projects? I'm fuzzy on
this. Can we add support for sensors that basically have no datasheet,
but that David has reverse engineered?
IIO Community Hindsight: Jason Kridner
Jason gave a presentation and also showed off some beaglebone devices at
the technical showcase. Jason noted in his presentation that he'd like
to see additional sensor support in IIO.
next reply other threads:[~2017-03-05 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 23:52 Alison Schofield [this message]
2017-03-06 3:31 ` Linux ELC & OpenIoT Report Matt Ranostay
2017-03-06 8:04 ` Jonathan Cameron
2017-03-06 11:58 ` Lars-Peter Clausen
2017-03-06 20:19 ` Alison Schofield
2017-03-06 21:29 ` David Lechner
2017-03-13 20:25 ` 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=20170305235202.GA6202@d830.WORKGROUP \
--to=amsfield22@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.