From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 6 Mar 2017 12:19:11 -0800 From: Alison Schofield To: Jonathan Cameron , david@lechnology.com Cc: linux-iio@vger.kernel.org Subject: Re: Linux ELC & OpenIoT Report Message-ID: <20170306201911.GA4278@d830.WORKGROUP> References: <20170305235202.GA6202@d830.WORKGROUP> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-ID: On Mon, Mar 06, 2017 at 08:04:21AM +0000, Jonathan Cameron wrote: > > > On 5 March 2017 23:52:04 GMT+00:00, Alison Schofield wrote: > >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 8< ......... snipped a bunch to focus on the ev3 sensor ............... > >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? > > Sure we can. Lots of drivers in the wider kernel are reverse engineered. A few in IIO may well have been. > > Hmm would take a slightly brave outreach y candidate perhaps. > I'm going to try to pull David in here, so he can fill in & correct me. I think David has kernel drivers he has written (loadable kernel modules - not user space drivers) that could be pushed upstream. (still could take significant bravery I guess) David, Am I getting anything right here? And, are there any destined for IIO? Thanks, alisons