[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3A356534-FEB0-4E0D-A8C8-922EEF1E0926@computer.org>
Date: Fri, 1 Jun 2018 18:37:36 +0200
From: "H. Nikolaus Schaller" <hns@...puter.org>
To: Pavel Machek <pavel@....cz>
Cc: Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Andreas Kemnade <andreas@...nade.info>,
Arnd Bergmann <arnd@...db.de>,
Marcel Holtmann <marcel@...tmann.org>,
Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/8] gnss: add new GNSS subsystem
Hi Pavel,
> Am 01.06.2018 um 18:26 schrieb Pavel Machek <pavel@....cz>:
>
> NMEA would not be my first choice, really. I'd propose something very
> similar to existing /dev/input/eventX, but with wider data types.
Since even Rome wasn't built in a day, my first choice is NMEA, but I am
open to anything on higher level to come second.
What about iio?
It is quite flexible and extensible and GNSS coordinates are a not very
different from accelerometer, gyroscope or compass data as all of them
describe the position and orientation, maybe speed of the device these
things are built into (at least for mobile devices).
--hns
Powered by blists - more mailing lists