linux-kernel - Re: [RFP] iio: Support of gesture sensor as a standard IIO sensor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 28 Jan 2018 09:38:29 +0000
From:   Jonathan Cameron <jic23@...nel.org>
To:     Pavel Machek <pavel@....cz>
Cc:     "Pandruvada, Srinivas" <srinivas.pandruvada@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>
Subject: Re: [RFP] iio: Support of gesture sensor as a standard IIO sensor

On Sun, 28 Jan 2018 09:40:03 +0100
Pavel Machek <pavel@....cz> wrote:

> hi!
> 
> > > > Correct. This will depend on  the firmware expected format . I
> > > > think
> > > > ultimately it will be standardized.  
> > > Is it fair to say that "expected" format is some kind of bytecode for
> > > CPU in the gesture sensor?  
> > Not necessarily a byte code to execute on the CPU in the gesture
> > sensor, but a format the code running on that CPU understands the way
> > gestures are formatted.
> > But it can be byte code for some manufacturers, so idea is just pass to
> > the firmware and let it process it an opaque format.  
> 
> It would be really good to figure out common format for different
> sensors. Otherwise kernel is not providing proper hardware
> abstraction.
> 
> 									Pavel

A common format, if it is byte code, would require in kernel compilers
for the various sensors.  Not going to happen.

Common format for everything other than the 'load magic firmware' part
might be doable. As in we can describe what the magic firmware is
doing...

Jonathan