From MAILER-DAEMON Sun Jul 01 00:40:59 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SlBxz-00005Y-SP
	for mharc-gpsd-dev@gnu.org; Sun, 01 Jul 2012 00:40:59 -0400
Received: from eggs.gnu.org ([208.118.235.92]:59570)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlBxt-0008SM-Tq
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 00:40:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlBxs-0001Js-0t
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 00:40:53 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:52696 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlBxr-0001JU-Sw
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 00:40:51 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id D03C74067B; Sun,  1 Jul 2012 00:40:46 -0400 (EDT)
Date: Sun, 1 Jul 2012 00:40:46 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Hal Murray <hmurray@megapathdsl.net>
Message-ID: <20120701044046.GA13222@thyrsus.com>
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 04:40:56 -0000

Hal Murray <hmurray@megapathdsl.net>:
> > It's time for a snap release due to the leap-second change!
> 
> Why the "snap"?.  This one is over and the next one won't happen for a year 
> or two.

Because the leap-second constant in the existing binary packages (used
before the sensor gets leap-second from the sats) is 15.  As of about
36 minutes ago that value is wrong.

I'd like the window during which it's wrong to be as short as possible.  
I can't fix the delays in propagating new packages after we ship, but
a snap release will avoid making it any longer than other stages in the
delivery chain enforce.

Yes, it's only one second.  Sue me, I'm a perfectionist.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Sun Jul 01 07:25:38 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SlIHa-0000vv-3x
	for mharc-gpsd-dev@gnu.org; Sun, 01 Jul 2012 07:25:38 -0400
Received: from eggs.gnu.org ([208.118.235.92]:36532)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlIHX-0000tc-Ht
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 07:25:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlIHV-0007V9-Qs
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 07:25:35 -0400
Received: from fnord.ir.bbn.com ([192.1.100.210]:61716)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlIHV-0007V1-N6
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 07:25:33 -0400
Received: by fnord.ir.bbn.com (Postfix, from userid 10853)
	id 42B4BA7E4; Sun,  1 Jul 2012 07:25:31 -0400 (EDT)
From: Greg Troxel <gdt@ir.bbn.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
	<20120701044046.GA13222@thyrsus.com>
OpenPGP: id=32611E25
X-Hashcash: 1:20:120701:esr@thyrsus.com::b+HCyL9nsb3jVuTo:000ns2
X-Hashcash: 1:20:120701:hmurray@megapathdsl.net::b+HCyL9nsb3jVuTo:0000000000000000000000000000000000000020+5
X-Hashcash: 1:20:120701:gpsd-dev@nongnu.org::b+HCyL9nsb3jVuTo:00000000000000000000000000000000000000000032mG
Date: Sun, 01 Jul 2012 07:25:16 -0400
In-Reply-To: <20120701044046.GA13222@thyrsus.com> (Eric S. Raymond's message
	of "Sun, 1 Jul 2012 00:40:46 -0400")
Message-ID: <rmi62a77mg3.fsf@fnord.ir.bbn.com>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 192.1.100.210
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 11:25:36 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


"Eric S. Raymond" <esr@thyrsus.com> writes:

> Hal Murray <hmurray@megapathdsl.net>:
>> > It's time for a snap release due to the leap-second change!
>>=20
>> Why the "snap"?.  This one is over and the next one won't happen for a y=
ear=20
>> or two.
>
> Because the leap-second constant in the existing binary packages (used
> before the sensor gets leap-second from the sats) is 15.  As of about
> 36 minutes ago that value is wrong.

As much as I don't like having packages download bits, it might be nice
to have a leap second file and a way to grab the new one from usno, so
that release and leap second update can be decoupled.  But it may not be
worth the effort, since it seems to only affect a few devices which are
arguably broken by design.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (NetBSD)

iEYEARECAAYFAk/wM5wACgkQ+vesoDJhHiUBDgCeLSGky+6ipWpVkwzjBlb22HcV
iTwAn1p49sD6Vpti5G+B4r2Kx22zKyTC
=/Yr4
-----END PGP SIGNATURE-----
--=-=-=--


From MAILER-DAEMON Sun Jul 01 11:12:10 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SlLoo-00075A-8f
	for mharc-gpsd-dev@gnu.org; Sun, 01 Jul 2012 11:12:10 -0400
Received: from eggs.gnu.org ([208.118.235.92]:45750)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlLol-00073a-8S
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:12:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlLoj-00044w-9t
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:12:06 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:54679 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SlLoj-00044f-5q
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:12:05 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id 0F8DB4067B; Sun,  1 Jul 2012 11:11:58 -0400 (EDT)
Date: Sun, 1 Jul 2012 11:11:58 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Greg Troxel <gdt@ir.bbn.com>
Message-ID: <20120701151158.GA9778@thyrsus.com>
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
	<20120701044046.GA13222@thyrsus.com>
	<rmi62a77mg3.fsf@fnord.ir.bbn.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6"
Content-Disposition: inline
In-Reply-To: <rmi62a77mg3.fsf@fnord.ir.bbn.com>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 15:12:08 -0000


--IJpNTDwzlM2Ie8A6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greg Troxel <gdt@ir.bbn.com>:
> As much as I don't like having packages download bits, it might be nice
> to have a leap second file and a way to grab the new one from usno, so
> that release and leap second update can be decoupled.  But it may not be
> worth the effort, since it seems to only affect a few devices which are
> arguably broken by design.

The obvious problem case is Evermore chips in binary mode, which report
only GPS week and TOW for time but never the leap-second offset.  There
aren't any other devices where this is known to be a problem, but that
qualifier "where this is known" worries me.=20

Your idea is potentially interesting, but not something I want to try
shipping without time for thought and testing.  I think it's best to apply
the simple stopgap fix now, then consider more permanent solutions at
leisure.
--=20
		<a href=3D"http://www.catb.org/~esr/">Eric S. Raymond</a>

--IJpNTDwzlM2Ie8A6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFP8Gi+rfUW04Qh8RwRAm1YAKCnUk1yVxeA9BZttnSRuEk6GTI5PACfXW3v
dxII+pYqolW1sSw5rZ2LrZE=
=Xf+q
-----END PGP SIGNATURE-----

--IJpNTDwzlM2Ie8A6--


From MAILER-DAEMON Sun Jul 01 11:15:50 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SlLsM-0007qI-3m
	for mharc-gpsd-dev@gnu.org; Sun, 01 Jul 2012 11:15:50 -0400
Received: from eggs.gnu.org ([208.118.235.92]:43896)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlLsJ-0007qB-64
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:15:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlLsH-00053f-Bk
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:15:46 -0400
Received: from fnord.ir.bbn.com ([192.1.100.210]:61357)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1SlLsG-000520-VI
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 11:15:45 -0400
Received: by fnord.ir.bbn.com (Postfix, from userid 10853)
	id 46686A7E4; Sun,  1 Jul 2012 11:15:43 -0400 (EDT)
From: Greg Troxel <gdt@ir.bbn.com>
To: esr@thyrsus.com
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
	<20120701044046.GA13222@thyrsus.com>
	<rmi62a77mg3.fsf@fnord.ir.bbn.com> <20120701151158.GA9778@thyrsus.com>
OpenPGP: id=32611E25
X-Hashcash: 1:20:120701:gpsd-dev@nongnu.org::b10IKIl0Zt+/ZQ/j:0000000000000000000000000000000000000000000WQa
X-Hashcash: 1:20:120701:hmurray@megapathdsl.net::b10IKIl0Zt+/ZQ/j:0000000000000000000000000000000000000038yf
X-Hashcash: 1:20:120701:esr@thyrsus.com::b10IKIl0Zt+/ZQ/j:006CRs
Date: Sun, 01 Jul 2012 11:15:43 -0400
In-Reply-To: <20120701151158.GA9778@thyrsus.com> (Eric S. Raymond's message of
	"Sun, 1 Jul 2012 11:11:58 -0400")
Message-ID: <rmifw9b5x7k.fsf@fnord.ir.bbn.com>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 192.1.100.210
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 15:15:48 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


"Eric S. Raymond" <esr@thyrsus.com> writes:

> Greg Troxel <gdt@ir.bbn.com>:
>> As much as I don't like having packages download bits, it might be nice
>> to have a leap second file and a way to grab the new one from usno, so
>> that release and leap second update can be decoupled.  But it may not be
>> worth the effort, since it seems to only affect a few devices which are
>> arguably broken by design.
>
> The obvious problem case is Evermore chips in binary mode, which report
> only GPS week and TOW for time but never the leap-second offset.  There
> aren't any other devices where this is known to be a problem, but that
> qualifier "where this is known" worries me.=20

So perhaps it's not worth a lot of effort.

> Your idea is potentially interesting, but not something I want to try
> shipping without time for thought and testing.  I think it's best to apply
> the simple stopgap fix now, then consider more permanent solutions at
> leisure.

Agreed - I didn't mean to suggest something immediate, just a thought
for the future, maybe before the next leap second.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (NetBSD)

iEYEARECAAYFAk/waZ8ACgkQ+vesoDJhHiUaaQCglYnID5rsenrgqwzjHBodxKWK
GMcAnjjQGIPowZMnJQ/Yyc4S7siL6hDZ
=tXcq
-----END PGP SIGNATURE-----
--=-=-=--


From MAILER-DAEMON Sun Jul 01 16:46:15 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SlR27-0005fT-Ba
	for mharc-gpsd-dev@gnu.org; Sun, 01 Jul 2012 16:46:15 -0400
Received: from eggs.gnu.org ([208.118.235.92]:36127)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SlR22-0005fL-Jm
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 16:46:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SlR1y-0005LJ-00
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 16:46:10 -0400
Received: from catbert.rellim.com ([204.17.205.1]:53404)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SlR1x-0005J1-F4
	for gpsd-dev@nongnu.org; Sun, 01 Jul 2012 16:46:05 -0400
Received: from localhost (spidey.rellim.com [204.17.205.8])
	(authenticated bits=0)
	by catbert.rellim.com (8.14.5/8.14.5) with ESMTP id q61KjpbG019073
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
	for <gpsd-dev@nongnu.org>; Sun, 1 Jul 2012 13:45:51 -0700
X-DKIM: OpenDKIM Filter v2.3.2 catbert.rellim.com q61KjpbG019073
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert;
	t=1341175551; bh=qSZYpCLHrsvVoJUrDrvfKtSZOX1yU/V6al/wU283Vq4=;
	h=Date:From:Cc:Subject:Message-ID:In-Reply-To:References:
	Mime-Version:Content-Type;
	b=ONOpTFL+yU0hsG6vjX9A5tUIQFIzxrzNUZBy+prJ2HeZ+7QLza5hKgJKkaWmcsBcT
	J3pyQQSA658WqvSTjTFWQ==
Date: Sun, 1 Jul 2012 13:45:46 -0700
From: "Gary E. Miller" <gem@rellim.com>
Cc: gpsd-dev@nongnu.org
Message-ID: <20120701134546.0233b45c.gem@rellim.com>
In-Reply-To: <rmi62a77mg3.fsf@fnord.ir.bbn.com>
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
	<20120701044046.GA13222@thyrsus.com>
	<rmi62a77mg3.fsf@fnord.ir.bbn.com>
Organization: Rellim
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/Y5pDhsd72pfHxuLrcd02lIK";
	protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 204.17.205.1
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 20:46:14 -0000

--Sig_/Y5pDhsd72pfHxuLrcd02lIK
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Greg!

On Sun, 01 Jul 2012 07:25:16 -0400
Greg Troxel <gdt@ir.bbn.com> wrote:

> As much as I don't like having packages download bits, it might be
> nice to have a leap second file and a way to grab the new one from
> usno, so that release and leap second update can be decoupled.


+1

I update my local pci and vendor/products lists with update scripts.
I update my ssl CAs and SMART disk tables with update scripts.

So a simple CLI tool to do so has a lot of precedent.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/Y5pDhsd72pfHxuLrcd02lIK
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/wtv4ACgkQBmnRqz71OvOnZQCgskYKA2hykQUWgtSugSMM7zvJ
VHIAn1NdvWaTvvPQd2048y/p6xVVDpow
=cKhS
-----END PGP SIGNATURE-----

--Sig_/Y5pDhsd72pfHxuLrcd02lIK--


From MAILER-DAEMON Mon Jul 02 06:09:14 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SldZC-0007HA-CR
	for mharc-gpsd-dev@gnu.org; Mon, 02 Jul 2012 06:09:14 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60241)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@wildgooses.com>) id 1SldZ6-0007Gg-FA
	for gpsd-dev@nongnu.org; Mon, 02 Jul 2012 06:09:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lists@wildgooses.com>) id 1SldZ0-0004dR-61
	for gpsd-dev@nongnu.org; Mon, 02 Jul 2012 06:09:08 -0400
Received: from mail1.nippynetworks.com ([91.220.24.129]:54260)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@wildgooses.com>) id 1SldZ0-0004d6-09
	for gpsd-dev@nongnu.org; Mon, 02 Jul 2012 06:09:02 -0400
Received: from localhost (mail1.nippynetworks.com [127.0.0.1])
	by mail1.nippynetworks.com (Postfix) with ESMTP id 45D273404C9
	for <gpsd-dev@nongnu.org>; Mon,  2 Jul 2012 11:08:59 +0100 (BST)
X-Virus-Scanned: amavisd-new at nippynetworks.com
Received: from mail1.nippynetworks.com ([127.0.0.1])
	by localhost (mail1.nippynetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP id hBmuc9B2-ZYg for <gpsd-dev@nongnu.org>;
	Mon,  2 Jul 2012 11:08:59 +0100 (BST)
Received: from Ed-Wildgooses-MacBook-Pro.local (unknown [212.69.38.73])
	(Authenticated sender: edward@wildgooses.com)
	by mail1.nippynetworks.com (Postfix) with ESMTPSA id 130113404C8
	for <gpsd-dev@nongnu.org>; Mon,  2 Jul 2012 11:08:58 +0100 (BST)
Message-ID: <4FF1733A.6070206@wildgooses.com>
Date: Mon, 02 Jul 2012 11:08:58 +0100
From: Ed W <lists@wildgooses.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: gpsd-dev@nongnu.org
References: <20120701010845.1654C4067B@snark.thyrsus.com>
	<20120701025731.DCEE580006F@ip-64-139-1-69.sjc.megapath.net>
	<20120701044046.GA13222@thyrsus.com>
	<rmi62a77mg3.fsf@fnord.ir.bbn.com>
	<20120701134546.0233b45c.gem@rellim.com>
In-Reply-To: <20120701134546.0233b45c.gem@rellim.com>
X-TagToolbar-Keys: D20120702110858725
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 91.220.24.129
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 10:09:12 -0000

On 01/07/2012 21:45, Gary E. Miller wrote:
> Yo Greg!
>
> On Sun, 01 Jul 2012 07:25:16 -0400
> Greg Troxel <gdt@ir.bbn.com> wrote:
>
>> As much as I don't like having packages download bits, it might be
>> nice to have a leap second file and a way to grab the new one from
>> usno, so that release and leap second update can be decoupled.
>
> +1
>
> I update my local pci and vendor/products lists with update scripts.
> I update my ssl CAs and SMART disk tables with update scripts.
>
> So a simple CLI tool to do so has a lot of precedent.
>
> RGDS
> GARY
>

The chrony guys already had something like this debate (admittedly quite 
some months before the event):
http://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2012/02/msg00027.html

The executive summary is that nothing is free, it can "cost" as much to 
maintain a database as shipping a release or relying on imperfect 
information.

Ed


From MAILER-DAEMON Wed Jul 04 03:04:28 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SmJdU-0000V3-Td
	for mharc-gpsd-dev@gnu.org; Wed, 04 Jul 2012 03:04:28 -0400
Received: from eggs.gnu.org ([208.118.235.92]:35058)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SmJdN-0000U2-KP
	for gpsd-dev@nongnu.org; Wed, 04 Jul 2012 03:04:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SmJdG-0003Jo-Tu
	for gpsd-dev@nongnu.org; Wed, 04 Jul 2012 03:04:21 -0400
Received: from mailout01.t-online.de ([194.25.134.80]:42869)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SmJdG-0003IX-KM
	for gpsd-dev@nongnu.org; Wed, 04 Jul 2012 03:04:14 -0400
Received: from fwd20.aul.t-online.de (fwd20.aul.t-online.de )
	by mailout01.t-online.de with smtp 
	id 1SmJdD-00045F-Fc; Wed, 04 Jul 2012 09:04:11 +0200
Received: from localhost
	(STD37vZlZhE9kVBsl4R2pIR1X2KB+dzpDxaPpNxd8RpCmaSIMGqJCFL-2E0d5QOgHP@[172.20.101.250])
	by fwd20.aul.t-online.de
	with esmtp id 1SmJd5-02eiIK0; Wed, 4 Jul 2012 09:04:03 +0200
MIME-Version: 1.0
Received: from 93.218.90.239:59522 by cmpweb16.aul.t-online.de with HTTP/1.1
	(NGCS V4-0-5-1 on API V3-11-7-2)
Date: Wed, 04 Jul 2012 09:04:03 +0200
To: "gpsd-dev" <gpsd-dev@nongnu.org>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-5-1
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: multipart/alternative;
	boundary="=_11eacdeefce0b1498e175bc70386f880"
Message-ID: <1SmJd5-02eiIK0@fwd20.aul.t-online.de>
X-ID: STD37vZlZhE9kVBsl4R2pIR1X2KB+dzpDxaPpNxd8RpCmaSIMGqJCFL-2E0d5QOgHP@t-dialin.net
X-TOI-MSGID: 9417348d-2ce2-4132-80ae-d8f4c55b9a5c
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.80
Subject: [gpsd-dev] A strange observation...
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 07:04:27 -0000

--=_11eacdeefce0b1498e175bc70386f880
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hello, 

	to verify the decodings of the nmea2000 driver, i use a "second" gpsd
on another port, and a second gpsmon. I observe a time difference
between these two gpsmon's. 

	Tracking down this observation, i start a a gpsmon  on the reference
gpsd (working on a bluetooth SIRF III GlobatSat BT 338) and a second
"gpsmon -n" connecting to the same gpsd. 

	These two gpsmon's show a time difference of of five seconds! 

	The gpsmon and gpsd a are build from HEAD of the git repository. The
hardware is a netbook with an intel atom and ubuntu 10.04 as operating
system. 

	I also what to note, that a few month ago, i can suspend this machine
with gpsd and gpsmon running, wake them, switch the BT 338 on again,
and the gpsmon starts to update the position again. With current
builds, i have to restart the gpsmon, often twice, to get the gpsmon
running again. But i am not sure, if this problem is introduced with
updates of gpsd or with updates of the operating system. 

	Reinhard
--=_11eacdeefce0b1498e175bc70386f880
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><title></title><meta http-equiv=3D"Content-Type" content=3D"tex=
t/html; charset=3DUTF-8"/></head><body><p style=3D"margin: 0px;">Hello,</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">to verify the decodings of the nmea2000 driver, i=
 use a "second" gpsd on another port, and a second gpsmon. I observe a time=
 difference between these two gpsmon's.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Tracking down this observation, i start a a gpsmo=
n  on the reference gpsd (working on a bluetooth SIRF III GlobatSat BT 338)=
 and a second "gpsmon -n" connecting to the same gpsd.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">These two gpsmon's show a time difference of of f=
ive seconds!</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">The gpsmon and gpsd a are build from HEAD of the =
git repository. The hardware is a netbook&nbsp;with an intel atom and ubunt=
u 10.04 as operating system.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">I also what to note, that a few month ago, i can =
suspend this machine with gpsd and gpsmon running, wake them, switch the BT=
 338 on again, and the gpsmon starts to update the position again. With cur=
rent builds, i have to restart the gpsmon, often twice, to get the gpsmon r=
unning again. But i am not sure, if this problem is introduced with updates=
 of gpsd or with updates&nbsp;of the operating system.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Reinhard</p></body></html>
--=_11eacdeefce0b1498e175bc70386f880--




From MAILER-DAEMON Thu Jul 05 21:05:46 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SmwzS-0001Ld-UY
	for mharc-gpsd-dev@gnu.org; Thu, 05 Jul 2012 21:05:46 -0400
Received: from eggs.gnu.org ([208.118.235.92]:53030)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SmwzQ-0001II-6C
	for gpsd-dev@nongnu.org; Thu, 05 Jul 2012 21:05:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1Smwhk-0002c6-PJ
	for gpsd-dev@nongnu.org; Thu, 05 Jul 2012 20:48:39 -0400
Received: from catbert.rellim.com ([204.17.205.1]:35500)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1Smwhk-0002Xy-7q
	for gpsd-dev@nongnu.org; Thu, 05 Jul 2012 20:47:28 -0400
Received: from localhost (spidey.rellim.com [204.17.205.8])
	(authenticated bits=0)
	by catbert.rellim.com (8.14.5/8.14.5) with ESMTP id q660lCgR017253
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Thu, 5 Jul 2012 17:47:13 -0700
X-DKIM: OpenDKIM Filter v2.3.2 catbert.rellim.com q660lCgR017253
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert;
	t=1341535634; bh=paH/GDmC7EqwC+j7NkAZV+HS+mRaHVcURRivZ2BFxEs=;
	h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:
	Mime-Version:Content-Type;
	b=TMnwvtYMb/EG5CQqKxCYY8jWVTDlAzKz/7jD1gNhWDtdpAnW11ZtRYaEwnPyH1eOt
	SGefCeLY3fL6NCMHV++Hg==
Date: Thu, 5 Jul 2012 17:47:06 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Message-ID: <20120705174706.40b4cd17.gem@rellim.com>
In-Reply-To: <1SmJd5-02eiIK0@fwd20.aul.t-online.de>
References: <1SmJd5-02eiIK0@fwd20.aul.t-online.de>
Organization: Rellim
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/62+lLIInPWYN7Fg.LUHo32A";
	protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 204.17.205.1
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] A strange observation...
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 01:05:45 -0000

--Sig_/62+lLIInPWYN7Fg.LUHo32A
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Reinhard.Arlt@t-online.de!

On Wed, 04 Jul 2012 09:04:03 +0200
"Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de> wrote:

> 	These two gpsmon's show a time difference of of five seconds!=20

A lot of GPS went nuts when the leap second happened.  My Holux-213U
reported a number of different offsets, but now seems to be settles
on an error of 10 seconds.  My daughters TomTom Via will not lock on
anything now and needs a urgent formware update.

The trick is to know which of the GPS is wacko.  Or maybe both of
them are.  Only way to know is to add a few network chimers into your
ntp.conf.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/62+lLIInPWYN7Fg.LUHo32A
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/2NZAACgkQBmnRqz71OvPouQCgiEtPLCUSyvUn4iCNTqiq/H7v
xBoAoN0NPkBtBronkbhPzQKZoFsSmwE6
=bt11
-----END PGP SIGNATURE-----

--Sig_/62+lLIInPWYN7Fg.LUHo32A--


From MAILER-DAEMON Sun Jul 08 12:19:47 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SnuD5-0007xq-6x
	for mharc-gpsd-dev@gnu.org; Sun, 08 Jul 2012 12:19:47 -0400
Received: from eggs.gnu.org ([208.118.235.92]:52550)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wouter@grep.be>) id 1SnbtP-0008Oi-SY
	for gpsd-dev@nongnu.org; Sat, 07 Jul 2012 16:46:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wouter@grep.be>) id 1SnbtN-0002As-Q8
	for gpsd-dev@nongnu.org; Sat, 07 Jul 2012 16:46:15 -0400
Received: from barbershop.grep.be ([89.106.240.122]:59248)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wouter@grep.be>) id 1SnbtN-0002AF-K9
	for gpsd-dev@nongnu.org; Sat, 07 Jul 2012 16:46:13 -0400
Received: from [190.181.128.164] (helo=carillon.nixsys.be)
	by grep.be with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.72) (envelope-from <wouter@grep.be>) id 1Snbtv-0006Pr-1N
	for gpsd-dev@nongnu.org; Sat, 07 Jul 2012 22:46:47 +0200
Received: from wouter by carillon.nixsys.be with local (Exim 4.80)
	(envelope-from <wouter@grep.be>) id 1SnbtC-0002qD-Ph
	for gpsd-dev@nongnu.org; Sat, 07 Jul 2012 22:46:02 +0200
Date: Sat, 7 Jul 2012 14:46:02 -0600
From: Wouter Verhelst <wouter@debian.org>
To: gpsd-dev@nongnu.org
Message-ID: <20120707204602.GA10139@grep.be>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8"
Content-Disposition: inline
X-Speed: Gates' Law: Every 18 months, the speed of software halves.
Organization: The Debian Project, http://www.debian.org/
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: "Wouter Verhelst,,," <wouter@grep.be>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 1)
X-Received-From: 89.106.240.122
X-Mailman-Approved-At: Sun, 08 Jul 2012 12:19:45 -0400
Subject: [gpsd-dev] HSPA modem/GPS receiver combo
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2012 20:46:17 -0000


--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

I've had a Lenovo X220 since slightly over a year now, and it came with
a HSPA modem built in. I've used it a fair number of times over that
year, but what I didn't realize (until about an hour or two ago) is that
it's actually a combined HSPA modem/GPS receiver. This may obviously
have something to do with the fact that it's not a GPS receiver until
the relevant bits are turned on.

A quick grep through the gpsd source code reveals that it doesn't seem
to be issuing any AT commands anywhere, so I wanted to add that myself;
but I can't actually seem to find what the best place to put them would
be.

In case this is something trivially simple for those of you more
familiar with the code than I am, turning on the relevant bits is done
like so:

AT*E2GPSCTL=3D1,1,1
AT*E2GPSNPD

which will then produce what (to my untrained eye) looks like an NMEA
stream on the device where this was issued. It's not possible to stop
this stream other than by closing the device file.

The E2GPSCTL command's options are used to select the mode (1 meaning
NMEA, if I understand things right; there are three other modes, but I'm
not sure what they mean); the interval between updates, in seconds
(range 0-60); and the final one is used to actually enable the GPS
receiver.

I should note that my particular device seems to ignore the timeout,
always using one-second intervals.

If this is trivial to add, I'd be happy to test patches. If it's not
trivial to add, I'd love it if someone could send me a pointer towards
some relevant documentation, so I can code it up myself and send a patch
in your general direction.

Thanks,

--=20
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a

--MGYHOYXEY6WxJCY8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJP+KAKAAoJEMKUD5Ub3wqdepcP/3BqWe2Y7kCOgCPIJ7dVSWI1
b7H5H7fTkGzYoCCbm8UF6sAQd1OO+UBpScGQWpD7HEFJNPVjz/cfni31AYGxQgO7
Lg7ie1yhSzVNQjiJK9UvCAl9YNUvd97PBxJj3fkl9us2RVexUN2hAMMjkA/ciyhF
ej28cRoTpedw5eCMZL1bWblr2PVsdBOtnC+ommlleru/0TESWND0FRrjwns100v5
ZI4vFuGqqOU5iBPeFJEOg4tVPnhh37j7bCN06ldS7QTHCL0Z+SVkHs8YOPmhOJVd
CTAGoFpT87s/NEdX0UjcypD8fviQ7Tt5ZhEMRaULNoU/JY2ENGSOmPKh6IiaEI3t
1EYxcyJAq8A68dIAwT9Nb+Avk2sAy0XVxtluNdGoxxS+8zx7Oa/RQfnhB+0UjGcB
P16N5B8Ci6XELSE5zoTx/t6AOGy7GWmnhmV9MVqCNaaTf7lyQojIM/gIXM+3MsBN
K2xLMvCi3PRjfZUS575XvemXw7PgO8Rpm6ELFxJ1rWXZAUzybBB2YEWID2oA/Ta8
pp8vDkrWmKoibwSo2BgM8yebs+pxEyZEuwnNOCwiq8TVhLeLviY+DgN67BP5t4H0
grh5C5nL5Q4xUK+4UN5mSIsBHGs1nhssdlPvmTmhmDVQBBPPbZzIDfNP5TpH/D4i
r2eC88WKrCBLNui1bHBd
=E3S/
-----END PGP SIGNATURE-----

--MGYHOYXEY6WxJCY8--


From MAILER-DAEMON Mon Jul 09 09:06:23 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoDfT-0004tt-Bg
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 09:06:23 -0400
Received: from eggs.gnu.org ([208.118.235.92]:33161)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SoDfL-0004tG-4s
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 09:06:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SoDfE-0003po-4d
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 09:06:14 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:44768)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SoDfD-0003oS-T6
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 09:06:08 -0400
Received: by yenl1 with SMTP id l1so10857512yen.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 06:06:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=o6CPxyedeeovxaJW3C9dRzeVLdqwI+WzhzNHk+nBtgk=;
	b=mo6h0y9zC0mp7L0/8BD+LgwkWKNwzG6kJ8W5kZzVRGTXcgJtqtcccNga0RvArf29H/
	+Oh5NeVlcrUigSpSezifXllU61ED5lCsbZxpYL6pCO/xDRsr61gnsF38vAGB4oOslesI
	3A7H7b+M03ekmlLKzOYmoz+GzGe8kw+YejSvk7X/bNGmYdBE01K7LWAO5m6PsNWwQlAc
	beBVRgRZEJSvGy/ynwLK9AM17SJHnPCMBo1sV6SiPsP0rtbSyGYgo4UFwomLMLyatyZW
	UGNGarR1+aPthuk20sgb+5679ce7+Hm9bnTK2+2Zqkg4BWVKeXG/9HeqkI5nSd/hPGn4
	f5Iw==
Received: by 10.236.109.225 with SMTP id s61mr48288418yhg.5.1341839164609;
	Mon, 09 Jul 2012 06:06:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.208.18 with HTTP; Mon, 9 Jul 2012 06:05:44 -0700 (PDT)
From: Olivier Cornu <o.cornu@gmail.com>
Date: Mon, 9 Jul 2012 15:05:44 +0200
Message-ID: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: multipart/alternative; boundary=20cf30363b09c0945a04c46546a2
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.173
Subject: [gpsd-dev] Using multiple location sources to improve accuracy and
	reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 13:06:21 -0000

--20cf30363b09c0945a04c46546a2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,


Every summer holidays i'm lucky enough to spend a few weeks sailing the
seven seas. A pretty good opportunity to using and tinkering with gpsd.

A couple years ago, i stumbled upon the infamous multipacket bug while
serializing location data from my smartphone to gpsd over bluetooth; This
smartphone was the only GPS device on board at the time.
Two summers later, there are now 7 GPS devices on board (4 smartphones and
3 USB dongles). Of course, we never really meant to bring so many: GPS
technology has just become ubiquitous in the meantime.
Thus my interest this year has naturally shifted to the way gpsd handles
multiple location devices.


What i've seen in the code so far reflects what i experience when i plug 2
GPS devices: what i'd call "basic multiplexing". That is, the client app
receives data from both devices, pretty much as they broadcast it.
Typically it means that, plotting my position on a map while moving in a
straight line, the boat is shown moving in a saw-teeth pattern,
alternatively jumping from one GPS' "trace" to the other's.
Worse: after i plugged the second GPS, my client once received a valid
"0=B0N, 0=B0E" position at some point (probably as the device acquired a fi=
x
for the first time, but i did not fully investigate it). It seems gpsd was
perfectly happy with sending my client app two positions thousands of miles
away from each other within the same split-second.
I wasn't. This is clearly not what i expected.

What did i expect? Put simply: more than basic multiplexing.
I expected to gain something from device redundancy: either improved
accuracy (reduced statistical error using several measures) or improved
reliability (if one device starts behaving incorrectly), or both. It seems
i get none.
Or, should i say, only the bare minimum in added reliability that
multiplexing happens to provide: i.e. if you've got two GPS and one becomes
silent, you still get one location source talking.
It seems like there is much more than can be harvested from redundancy of
GPS devices; I don't like witnessing wasted resources. ;-)

Besides, accuracy and reliability are not secondary topics or optional
features for a software such as gpsd. In critical conditions, they are
potential life-savers. At least, i consider they'll become such for me
during the coming year.
Such features also appear to belong to gpsd, not clients, nor another proxy
layer between them: accurate and reliable location information is
precisely what most clients expect from gpsd itself.
Clients that care about underlying devices (and their individual states)
can always request extensive raw data. However, i believe most clients only
want the best location information you can feed them, no matter how you
achieve it nor where it came from. Thus, that should be the default
behavior, imho.


Using redundancy in order to provide the best service possible means it is
not enough to blindly relay GPS data: gpsd would have to maintain its own
unique internal location state, that GPS devices would only contribute to.
Gpsd would have to be more than a transparent hub designed to hide
proprietary protocols (and bugs) and broadcast GPS messages to clients. It
would have to become a location provider in its own right, actively
mangling with raw GPS data for the best.

Practically speaking, what kind of mangling am i talking about?
Simple example: to my knowledge most commercial airplanes use 3 different
location sources. They select the middle longitude and middle latitude from
these 3 sources in order to compute their position. Doing so makes the
overall location a bit more accurate and way more reliable. Of course,
possibilities are not limited to this.
In the current architecture, the piece of code updating the internal
location state would be run by the multiplexer when new data becomes
available from a device (gpsd.c:consume_packets()).


What am i getting wrong so far?
Is there any chance trunk might come this way, or will i have to hack a
solution tailored for my use case?

Thanks,

--
Olivier Cornu

--20cf30363b09c0945a04c46546a2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,<div><br></div><div><br></div><div>Every summer holidays i&#39;m luc=
ky enough to spend a few weeks sailing the seven seas. A pretty good opport=
unity to using and tinkering with gpsd.</div><div><br></div><div>A couple y=
ears ago, i stumbled upon the infamous multipacket bug while serializing lo=
cation data from my smartphone to gpsd over bluetooth; This smartphone was =
the only GPS device on board at the time.</div>

<div>Two summers later, there are now 7 GPS devices on board (4 smartphones=
 and 3 USB dongles). Of course, we never really meant to bring so many: GPS=
 technology has just become ubiquitous in the meantime.</div><div>Thus my i=
nterest this year has naturally shifted to the way gpsd handles multiple lo=
cation devices.</div>

<div><br></div><div><br></div><div>What i&#39;ve seen in the code so far re=
flects what i experience when i plug 2 GPS devices: what i&#39;d call &quot=
;basic multiplexing&quot;. That is, the client app receives data from both =
devices, pretty much as they broadcast it.</div>

<div>Typically it means that, plotting my position on a map while moving in=
 a straight line, the boat is shown moving in a saw-teeth pattern, alternat=
ively jumping from one GPS&#39; &quot;trace&quot; to the other&#39;s.</div>

<div>Worse: after i plugged the second GPS, my client once received a valid=
 &quot;0=B0N, 0=B0E&quot; position at some point (probably as the device ac=
quired a fix for the first time, but i did not fully investigate it). It se=
ems gpsd was perfectly happy with sending my client app two positions thous=
ands of miles away from each other within the same split-second.</div>

<div>I wasn&#39;t.=A0This is clearly not what i expected.</div><div><br></d=
iv><div>What did i expect? Put simply: more than basic multiplexing.</div><=
div>I expected to gain something from device redundancy: either improved ac=
curacy (reduced statistical error using several measures) or improved relia=
bility (if one device starts behaving incorrectly), or both.=A0It seems i g=
et none.</div>

<div>Or, should i say, only the bare minimum in added reliability that mult=
iplexing happens to provide: i.e. if you&#39;ve got two GPS and one becomes=
 silent, you still get one location source talking.</div><div>It seems like=
 there is much more than can be harvested from redundancy of GPS devices; I=
 don&#39;t like witnessing wasted resources. ;-)</div>

<div><br></div><div>Besides, accuracy and reliability are not secondary top=
ics or optional features for a software such as gpsd. In critical condition=
s, they=A0are potential life-savers. At least, i consider they&#39;ll becom=
e such for me during the coming year.</div>

<div>Such features also appear to belong to gpsd, not clients, nor another =
proxy layer between them: accurate and reliable location information is pre=
cisely=A0what most clients expect from gpsd itself.</div><div>Clients that =
care about underlying devices (and their individual states) can always requ=
est extensive raw data. However, i believe most clients only want the best =
location information you can feed them, no matter how you achieve it nor wh=
ere it came from. Thus, that should be the default behavior, imho.</div>

<div><br></div><div><br></div><div>Using redundancy in order to provide the=
 best service possible means it is not enough to blindly relay GPS data:=A0=
gpsd would have to maintain its own unique internal location state, that GP=
S devices would only contribute to.</div>

<div>Gpsd would have to be more than a transparent hub designed to hide pro=
prietary protocols (and bugs) and broadcast GPS messages to clients. It wou=
ld have to become a location provider in its own right, actively mangling w=
ith raw GPS data for the best.</div>

<div><br></div><div>Practically speaking, what kind of mangling am i talkin=
g about?</div><div>Simple example: to my knowledge most commercial airplane=
s use 3 different location sources. They select the middle longitude and mi=
ddle latitude from these 3 sources in order to compute their position. Doin=
g so makes the overall location a bit more accurate and way more reliable. =
Of course, possibilities are not limited to this.</div>

<div><div>In the current architecture, the piece of code updating the inter=
nal location state would be run by the multiplexer when new data becomes av=
ailable from a device (gpsd.c:consume_packets()).</div></div><div><br>
</div>
<div><br></div><div>What am i getting wrong so far?</div><div>Is there any =
chance trunk might come this way, or will i have to hack a solution tailore=
d for my use case?</div><div><br></div><div>Thanks,</div><div><br></div>

<div>--<br>Olivier Cornu</div><div><div><br></div></div>

--20cf30363b09c0945a04c46546a2--


From MAILER-DAEMON Mon Jul 09 13:23:21 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoHg9-00068O-7d
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 13:23:21 -0400
Received: from eggs.gnu.org ([208.118.235.92]:44266)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHg6-00067b-BN
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:23:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHg4-0006hT-OP
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:23:17 -0400
Received: from mail-gh0-f173.google.com ([209.85.160.173]:38854)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHg4-0006hA-H0
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:23:16 -0400
Received: by ghrr14 with SMTP id r14so11171848ghr.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 10:23:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=aTjkhmOCtkewJh1SjUJxxQ7GIOTFECIxRoEpyuTElb0=;
	b=z4BbT/RB39isTy1/5/uCqYhBrtZy96aKUNcZUznMTaGmmCBqGH1bXMzVu6M22/DZpt
	4ECNQniJnrtTqnWef3NI+MHWYtaQMlwGXaMlSdm2dEvE7OgYTymPIEDp2mjXrAAhxYDh
	AqdyV6kg4YW3TDIUjkT8Md27Qsk5uUXaDV8FmcXuoPzgMkj7bN9FOTOC9++efqPmmnYs
	SgfcpV649j25ut6xfHtup8W9HXEiPADl7TNktQAiMQRJw4EgY7U2jhrnmoModAbUe30s
	IEZmlWhNnX3UHCNpgjve0AZ/F9LEOGT1ZdMFQd5GEU7nIUcpQOEVvufPTqkfMci9Il9O
	JwlQ==
Received: by 10.66.74.69 with SMTP id r5mr66979269pav.56.1341854593624; Mon,
	09 Jul 2012 10:23:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.47.193 with HTTP; Mon, 9 Jul 2012 10:22:53 -0700 (PDT)
In-Reply-To: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
From: Chris Kuethe <chris.kuethe@gmail.com>
Date: Mon, 9 Jul 2012 10:22:53 -0700
Message-ID: <CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
To: Olivier Cornu <o.cornu@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:23:19 -0000

On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu <o.cornu@gmail.com> wrote:
> What am i getting wrong so far?
> Is there any chance trunk might come this way, or will i have to hack a
> solution tailored for my use case?

GPSD is intended to be a multiplexer, not a software solver. There are
a number of use cases for having multiple sensors reporting back to
gpsd without it trying to fuse all those reports.

A lazy search for "Garmin G1000 installation manual" doesn't give me
any documentation on how to install one in an airplane. I bet there's
a specification on where the receiver and antennas must be installed,
and then a calibration screen for entering the specifics of that
particular aircraft. You're going to need to do something similar -
think on the issues and try some experiments if you want to do sensor
fusion.

-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?


From MAILER-DAEMON Mon Jul 09 13:25:46 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoHiU-0006J4-Jk
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 13:25:46 -0400
Received: from eggs.gnu.org ([208.118.235.92]:42246)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHiS-0006Iv-9w
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:25:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHiQ-0007VU-Fx
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:25:43 -0400
Received: from mail-gh0-f173.google.com ([209.85.160.173]:49748)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHiQ-0007TL-8u
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:25:42 -0400
Received: by ghrr14 with SMTP id r14so11174849ghr.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 10:25:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=XuZFXwXsj42DRdMrFXx3ywYW9XaIoxWKbPD8Ua4ki08=;
	b=GJldfAFYYC+y6O4HGjG4LQp/uqicxl7EeSIbt3GwqufH3TOg6ndL3kjSxNlb/6okmV
	hFMnH2Q5bUgq8D/PTGhuXt/HIs3wJZ/UuGEhon11/qTf0RGXKSlp7k3zrygY8MifMK5f
	LHzUbW8JOXP+jU7lA2FemRWu3OhFxaFHNhwt0QanFwscuyoVpqDFg362LbHduDkktV08
	GBKn3S+f740QfTIVnQX4vC9UUMopPXiPF1RMq/0QG5pGtob3pNkKTXfsW495jvZ40hBw
	NKtfXI9PqVR5Xcgj6LE5hRKbxjs1nTZDNnkGz+Tof5w+MxHBQU72LHuYQe24AWHhc3cd
	JZfQ==
MIME-Version: 1.0
Received: by 10.60.7.197 with SMTP id l5mr40574832oea.33.1341854738767; Mon,
	09 Jul 2012 10:25:38 -0700 (PDT)
Received: by 10.182.72.73 with HTTP; Mon, 9 Jul 2012 10:25:38 -0700 (PDT)
Received: by 10.182.72.73 with HTTP; Mon, 9 Jul 2012 10:25:38 -0700 (PDT)
In-Reply-To: <CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
Date: Mon, 9 Jul 2012 12:25:38 -0500
Message-ID: <CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
From: Richard Allen <rsaxvc@gmail.com>
To: Chris Kuethe <chris.kuethe@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f83a1630b60ee04c468e715
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:25:45 -0000

--e89a8f83a1630b60ee04c468e715
Content-Type: text/plain; charset=ISO-8859-1

I believe that particular product is installed by the manufacturer or by a
certified retrofit shop.
On Jul 9, 2012 12:23 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:

> On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu <o.cornu@gmail.com> wrote:
> > What am i getting wrong so far?
> > Is there any chance trunk might come this way, or will i have to hack a
> > solution tailored for my use case?
>
> GPSD is intended to be a multiplexer, not a software solver. There are
> a number of use cases for having multiple sensors reporting back to
> gpsd without it trying to fuse all those reports.
>
> A lazy search for "Garmin G1000 installation manual" doesn't give me
> any documentation on how to install one in an airplane. I bet there's
> a specification on where the receiver and antennas must be installed,
> and then a calibration screen for entering the specifics of that
> particular aircraft. You're going to need to do something similar -
> think on the issues and try some experiments if you want to do sensor
> fusion.
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?
>
>

--e89a8f83a1630b60ee04c468e715
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>I believe that particular product is installed by the manufacturer or by=
 a certified retrofit shop.</p>
<div class=3D"gmail_quote">On Jul 9, 2012 12:23 PM, &quot;Chris Kuethe&quot=
; &lt;<a href=3D"mailto:chris.kuethe@gmail.com">chris.kuethe@gmail.com</a>&=
gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu &lt;<a href=3D"mailto:o.cornu=
@gmail.com">o.cornu@gmail.com</a>&gt; wrote:<br>
&gt; What am i getting wrong so far?<br>
&gt; Is there any chance trunk might come this way, or will i have to hack =
a<br>
&gt; solution tailored for my use case?<br>
<br>
GPSD is intended to be a multiplexer, not a software solver. There are<br>
a number of use cases for having multiple sensors reporting back to<br>
gpsd without it trying to fuse all those reports.<br>
<br>
A lazy search for &quot;Garmin G1000 installation manual&quot; doesn&#39;t =
give me<br>
any documentation on how to install one in an airplane. I bet there&#39;s<b=
r>
a specification on where the receiver and antennas must be installed,<br>
and then a calibration screen for entering the specifics of that<br>
particular aircraft. You&#39;re going to need to do something similar -<br>
think on the issues and try some experiments if you want to do sensor<br>
fusion.<br>
<br>
--<br>
GDB has a &#39;break&#39; feature; why doesn&#39;t it have &#39;fix&#39; to=
o?<br>
<br>
</blockquote></div>

--e89a8f83a1630b60ee04c468e715--


From MAILER-DAEMON Mon Jul 09 13:29:35 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoHmB-0006YG-82
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 13:29:35 -0400
Received: from eggs.gnu.org ([208.118.235.92]:42751)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHm9-0006YA-0n
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:29:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHm7-0008Cu-7Q
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:29:32 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:35602)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHm6-0008Cn-Ui
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:29:31 -0400
Received: by pbbro12 with SMTP id ro12so21113040pbb.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 10:29:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=0YCjcpMLgcx3zD+KDLY2S2jr0I968lhXTsfg3oeyrew=;
	b=XInbncGPIBsl9P19MQHocB3BtLu5XLNCT+LOdL6cHxbHgGkN4sB/Q4uXAJ3OFYF2Nf
	c4H5aBNOTZgBiNAtUTpjLhez2vEOX+BL36PVxuZk1QeFt4dGEJJIMNYAEJclb1uMxi2q
	dCFG9qHq2ap9ib/xIxY3WIVXwV/h5pJi7Hp1sp8kAex7QWrYk4cWXTtSBUWwGTl9Lq3Z
	+LGvk3h8qzJHlLzmULTJLKaMmMvOAFJ+X2VJMhpueS2xw8/Xu/6TTOGD/ETclb9IbCCq
	C6lMgev8M5VtL5fwEpOi/SUmZowoshQrTuHiYSKggNEOCPoGvDY2mlbEG3QE10+nUy1V
	ysCw==
Received: by 10.68.232.197 with SMTP id tq5mr61292591pbc.53.1341854968506;
	Mon, 09 Jul 2012 10:29:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.47.193 with HTTP; Mon, 9 Jul 2012 10:29:08 -0700 (PDT)
In-Reply-To: <CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
	<CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
From: Chris Kuethe <chris.kuethe@gmail.com>
Date: Mon, 9 Jul 2012 10:29:08 -0700
Message-ID: <CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
To: Richard Allen <rsaxvc@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.45
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:29:34 -0000

On Mon, Jul 9, 2012 at 10:25 AM, Richard Allen <rsaxvc@gmail.com> wrote:
> I believe that particular product is installed by the manufacturer or by a
> certified retrofit shop.

Indeed.

I'm just saying that I don't see any documentation casually laying
around that describes the procedures for
installing/calibrating/maintaining such a device correctly, either for
aircraft or marine use. But simply averaging receivers is going to
cause problems.

> On Jul 9, 2012 12:23 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:
>>
>> On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu <o.cornu@gmail.com> wrote:
>> > What am i getting wrong so far?
>> > Is there any chance trunk might come this way, or will i have to hack a
>> > solution tailored for my use case?
>>
>> GPSD is intended to be a multiplexer, not a software solver. There are
>> a number of use cases for having multiple sensors reporting back to
>> gpsd without it trying to fuse all those reports.
>>
>> A lazy search for "Garmin G1000 installation manual" doesn't give me
>> any documentation on how to install one in an airplane. I bet there's
>> a specification on where the receiver and antennas must be installed,
>> and then a calibration screen for entering the specifics of that
>> particular aircraft. You're going to need to do something similar -
>> think on the issues and try some experiments if you want to do sensor
>> fusion.
>>
>> --
>> GDB has a 'break' feature; why doesn't it have 'fix' too?
>>
>



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?


From MAILER-DAEMON Mon Jul 09 13:33:16 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoHpk-0007fI-0d
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 13:33:16 -0400
Received: from eggs.gnu.org ([208.118.235.92]:59064)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHph-0007f9-5K
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:33:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHpf-0000f5-6l
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:33:12 -0400
Received: from mail-ob0-f173.google.com ([209.85.214.173]:33503)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rsaxvc@gmail.com>) id 1SoHpe-0000et-Ti
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:33:11 -0400
Received: by obbta14 with SMTP id ta14so20233554obb.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 10:33:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=AJwoAxdEkpR6mMjwQVfNPVrfGRNg90PnbZj4Rt0QmsQ=;
	b=hVGOG+2JRkTiQaKH/QAjw48Re81P4nqN4dbj7KdSGkZSJ/7QZ0M3zcXeXcBD6ZHdxF
	Y8j6WsKgzfHUUJxGR2e89uYGCDD3GbuXf9+Ps+ir7pbsVGfRLeoItAQx9L4cYQHJbD8x
	6hUSQKr3NrdYquTsqo6Gt4+CXJUt+4n92eHcvJejKsTRNSo9SJMcLGVkaeSLNNW1STkb
	wZZ3Q7RJxntBQE1LyA3IJy+pZ2QFbPoB+dJHz8C4b61gxRji3vaoKAzXF/nn8/xtd7b0
	G0ltVuNbRmg47J1a7jN5Ia9Dq3LeeicSRWHL4L9cpJjgwYJ5uZnQ0QU5e38aa10Sx7lj
	E9Gw==
MIME-Version: 1.0
Received: by 10.182.160.10 with SMTP id xg10mr36725725obb.76.1341855188899;
	Mon, 09 Jul 2012 10:33:08 -0700 (PDT)
Received: by 10.182.72.73 with HTTP; Mon, 9 Jul 2012 10:33:08 -0700 (PDT)
Received: by 10.182.72.73 with HTTP; Mon, 9 Jul 2012 10:33:08 -0700 (PDT)
In-Reply-To: <CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
	<CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
	<CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
Date: Mon, 9 Jul 2012 12:33:08 -0500
Message-ID: <CAENJYHobdFrhOg5dibkKoSOUEz-0VRkFa=+qubuLsMU1Yyt_MA@mail.gmail.com>
From: Richard Allen <rsaxvc@gmail.com>
To: Chris Kuethe <chris.kuethe@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0447f23adfd92604c469019f
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.214.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:33:14 -0000

--f46d0447f23adfd92604c469019f
Content-Type: text/plain; charset=ISO-8859-1

You could make a small software package that listens to all the raw feeds.
It then does some regression on a model of where the sensors are mounted,
and possibly feed it back to gpsd?
On Jul 9, 2012 12:29 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:

> On Mon, Jul 9, 2012 at 10:25 AM, Richard Allen <rsaxvc@gmail.com> wrote:
> > I believe that particular product is installed by the manufacturer or by
> a
> > certified retrofit shop.
>
> Indeed.
>
> I'm just saying that I don't see any documentation casually laying
> around that describes the procedures for
> installing/calibrating/maintaining such a device correctly, either for
> aircraft or marine use. But simply averaging receivers is going to
> cause problems.
>
> > On Jul 9, 2012 12:23 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:
> >>
> >> On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu <o.cornu@gmail.com>
> wrote:
> >> > What am i getting wrong so far?
> >> > Is there any chance trunk might come this way, or will i have to hack
> a
> >> > solution tailored for my use case?
> >>
> >> GPSD is intended to be a multiplexer, not a software solver. There are
> >> a number of use cases for having multiple sensors reporting back to
> >> gpsd without it trying to fuse all those reports.
> >>
> >> A lazy search for "Garmin G1000 installation manual" doesn't give me
> >> any documentation on how to install one in an airplane. I bet there's
> >> a specification on where the receiver and antennas must be installed,
> >> and then a calibration screen for entering the specifics of that
> >> particular aircraft. You're going to need to do something similar -
> >> think on the issues and try some experiments if you want to do sensor
> >> fusion.
> >>
> >> --
> >> GDB has a 'break' feature; why doesn't it have 'fix' too?
> >>
> >
>
>
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?
>

--f46d0447f23adfd92604c469019f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>You could make a small software package that listens to all the raw feed=
s. It then does some regression on a model of where the sensors are mounted=
, and possibly feed it back to gpsd?</p>
<div class=3D"gmail_quote">On Jul 9, 2012 12:29 PM, &quot;Chris Kuethe&quot=
; &lt;<a href=3D"mailto:chris.kuethe@gmail.com">chris.kuethe@gmail.com</a>&=
gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Jul 9, 2012 at 10:25 AM, Richard Allen &lt;<a href=3D"mailto:rsaxvc=
@gmail.com">rsaxvc@gmail.com</a>&gt; wrote:<br>
&gt; I believe that particular product is installed by the manufacturer or =
by a<br>
&gt; certified retrofit shop.<br>
<br>
Indeed.<br>
<br>
I&#39;m just saying that I don&#39;t see any documentation casually laying<=
br>
around that describes the procedures for<br>
installing/calibrating/maintaining such a device correctly, either for<br>
aircraft or marine use. But simply averaging receivers is going to<br>
cause problems.<br>
<br>
&gt; On Jul 9, 2012 12:23 PM, &quot;Chris Kuethe&quot; &lt;<a href=3D"mailt=
o:chris.kuethe@gmail.com">chris.kuethe@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu &lt;<a href=3D"mailt=
o:o.cornu@gmail.com">o.cornu@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt; What am i getting wrong so far?<br>
&gt;&gt; &gt; Is there any chance trunk might come this way, or will i have=
 to hack a<br>
&gt;&gt; &gt; solution tailored for my use case?<br>
&gt;&gt;<br>
&gt;&gt; GPSD is intended to be a multiplexer, not a software solver. There=
 are<br>
&gt;&gt; a number of use cases for having multiple sensors reporting back t=
o<br>
&gt;&gt; gpsd without it trying to fuse all those reports.<br>
&gt;&gt;<br>
&gt;&gt; A lazy search for &quot;Garmin G1000 installation manual&quot; doe=
sn&#39;t give me<br>
&gt;&gt; any documentation on how to install one in an airplane. I bet ther=
e&#39;s<br>
&gt;&gt; a specification on where the receiver and antennas must be install=
ed,<br>
&gt;&gt; and then a calibration screen for entering the specifics of that<b=
r>
&gt;&gt; particular aircraft. You&#39;re going to need to do something simi=
lar -<br>
&gt;&gt; think on the issues and try some experiments if you want to do sen=
sor<br>
&gt;&gt; fusion.<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; GDB has a &#39;break&#39; feature; why doesn&#39;t it have &#39;fi=
x&#39; too?<br>
&gt;&gt;<br>
&gt;<br>
<br>
<br>
<br>
--<br>
GDB has a &#39;break&#39; feature; why doesn&#39;t it have &#39;fix&#39; to=
o?<br>
</blockquote></div>

--f46d0447f23adfd92604c469019f--


From MAILER-DAEMON Mon Jul 09 13:41:36 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoHxo-000221-7x
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 13:41:36 -0400
Received: from eggs.gnu.org ([208.118.235.92]:56640)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHxm-00021t-5E
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:41:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHxj-0003NW-Fu
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:41:33 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:50531)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.kuethe@gmail.com>) id 1SoHxj-0003MC-6y
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 13:41:31 -0400
Received: by pbbro12 with SMTP id ro12so21129436pbb.4
	for <gpsd-dev@nongnu.org>; Mon, 09 Jul 2012 10:41:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=DAmzvVAVZY2VvSudnhITcaOkxTduOCbHjblqqnONObo=;
	b=ekyB/zV7SIjlm7MllZSBqeWHSSp6XQ/+KQKXebA4+lx6Y/gpNVipYYEgxxm5ARGxQy
	ONxLQdBwsYLyejnpKJQHGkO0+X6yPxNTvS/w1VNpZnDlZfcO3YSwiq8uDUAuY+O1MB5k
	FjHpSN9T7LCDlauc2TGOJrx9WuTJS9Mq1B/q9yqVz3cGcebsg1Qg+OknFLGN4RcyC9xJ
	ywXyoTdtlVCrl10TNkP2/jfvvUaEyTxvezuV8UezS9xIcbHBzQQ7UNLFVgWpP3G/diBg
	eXU+QmdTUpkz8uDDdj/QA+ZJNhYpps+ki8O0WeluhY2Tqas+OLA/yQXwgcHSMNYktPOo
	qm/Q==
Received: by 10.68.200.104 with SMTP id jr8mr30931974pbc.9.1341855688559; Mon,
	09 Jul 2012 10:41:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.47.193 with HTTP; Mon, 9 Jul 2012 10:41:08 -0700 (PDT)
In-Reply-To: <CAENJYHobdFrhOg5dibkKoSOUEz-0VRkFa=+qubuLsMU1Yyt_MA@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
	<CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
	<CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
	<CAENJYHobdFrhOg5dibkKoSOUEz-0VRkFa=+qubuLsMU1Yyt_MA@mail.gmail.com>
From: Chris Kuethe <chris.kuethe@gmail.com>
Date: Mon, 9 Jul 2012 10:41:08 -0700
Message-ID: <CAGHP0pLM7UpXPYo-L=8FN=Yq13SN04HWDB41jmo50WHBgcen-A@mail.gmail.com>
To: Richard Allen <rsaxvc@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.45
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:41:35 -0000

Yes, that's one approach. Be sure to consider:
- surveyed positions of your fixed antennas
- number of mobile devices
- size of vessel
- what happens under marginal signal conditions (do receivers claim to
have a good quality fix but at the wrong position)
- error detection/correction in the app
- loop detection, so that this app does not use its own output like
the output of a receiver.
...

web search for "gps attitude sensor" will give some hints on the
current state of the art.

On Mon, Jul 9, 2012 at 10:33 AM, Richard Allen <rsaxvc@gmail.com> wrote:
> You could make a small software package that listens to all the raw feeds.
> It then does some regression on a model of where the sensors are mounted,
> and possibly feed it back to gpsd?
>
> On Jul 9, 2012 12:29 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:
>>
>> On Mon, Jul 9, 2012 at 10:25 AM, Richard Allen <rsaxvc@gmail.com> wrote:
>> > I believe that particular product is installed by the manufacturer or by
>> > a
>> > certified retrofit shop.
>>
>> Indeed.
>>
>> I'm just saying that I don't see any documentation casually laying
>> around that describes the procedures for
>> installing/calibrating/maintaining such a device correctly, either for
>> aircraft or marine use. But simply averaging receivers is going to
>> cause problems.
>>
>> > On Jul 9, 2012 12:23 PM, "Chris Kuethe" <chris.kuethe@gmail.com> wrote:
>> >>
>> >> On Mon, Jul 9, 2012 at 6:05 AM, Olivier Cornu <o.cornu@gmail.com>
>> >> wrote:
>> >> > What am i getting wrong so far?
>> >> > Is there any chance trunk might come this way, or will i have to hack
>> >> > a
>> >> > solution tailored for my use case?
>> >>
>> >> GPSD is intended to be a multiplexer, not a software solver. There are
>> >> a number of use cases for having multiple sensors reporting back to
>> >> gpsd without it trying to fuse all those reports.
>> >>
>> >> A lazy search for "Garmin G1000 installation manual" doesn't give me
>> >> any documentation on how to install one in an airplane. I bet there's
>> >> a specification on where the receiver and antennas must be installed,
>> >> and then a calibration screen for entering the specifics of that
>> >> particular aircraft. You're going to need to do something similar -
>> >> think on the issues and try some experiments if you want to do sensor
>> >> fusion.
>> >>
>> >> --
>> >> GDB has a 'break' feature; why doesn't it have 'fix' too?
>> >>
>> >
>>
>>
>>
>> --
>> GDB has a 'break' feature; why doesn't it have 'fix' too?



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?


From MAILER-DAEMON Mon Jul 09 14:05:28 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoIKu-0005Xr-NH
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 14:05:28 -0400
Received: from eggs.gnu.org ([208.118.235.92]:53120)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoIKr-0005Xk-4T
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:05:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoIKo-0000pT-8j
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:05:24 -0400
Received: from catbert.rellim.com ([204.17.205.1]:38899)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoIKn-0000nh-Nh
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:05:22 -0400
Received: from localhost (spidey.rellim.com [204.17.205.8])
	(authenticated bits=0)
	by catbert.rellim.com (8.14.5/8.14.5) with ESMTP id q69I56GN031554
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Mon, 9 Jul 2012 11:05:06 -0700
X-DKIM: OpenDKIM Filter v2.3.2 catbert.rellim.com q69I56GN031554
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert;
	t=1341857107; bh=1qsN7Yg44B2rPy6yYOnYkXuIKzuwaMisc3w88ycvnyg=;
	h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:
	Mime-Version:Content-Type;
	b=I4Jnr6DfXIG6GavyNUKIWDpagbnAI+LBoFbXxpxywf0qRvSLDgqEPRk7yapQgBFXc
	b/KwFmwnTDbddXFDKM83A==
Date: Mon, 9 Jul 2012 11:05:02 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: Chris Kuethe <chris.kuethe@gmail.com>
Message-ID: <20120709110502.74079634.gem@rellim.com>
In-Reply-To: <CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
	<CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
	<CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
Organization: Rellim
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/v+/ps58rm/ZJiF/KjnvaSr4";
	protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 204.17.205.1
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:05:26 -0000

--Sig_/v+/ps58rm/ZJiF/KjnvaSr4
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Chris!

On Mon, 9 Jul 2012 10:29:08 -0700
Chris Kuethe <chris.kuethe@gmail.com> wrote:

> I'm just saying that I don't see any documentation casually laying
> around that describes the procedures for
> installing/calibrating/maintaining such a device correctly, either for
> aircraft or marine use.

There is a TSO that specifies GPS standards for aircraft usage.  They
require that aircraft GPS have one more sat in use for 3D than minimally
required for a fix.  Then the GPS computed altitude is compared to a
barometric altimeter.  If the multiple GPS solutions do not match each
other, or match the barometric altitude, then the GPS must flash a RAIM
error.

I could prolly dig out the TSO for you, but that above is basically all
the goodness you would get from it.

In a modern transport category aircraft the multiple GPS are just more
sensors, along with ILS, VOR, INS, radar altimeter, etc. that are fed
into the master nav computer.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/v+/ps58rm/ZJiF/KjnvaSr4
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/7HVEACgkQBmnRqz71OvPW6wCguKY/03k3aDI3rwQ+bMek5yFK
nRUAoIcuNaZE7zQgZ1sy5AlF4sRK3+kI
=n3zX
-----END PGP SIGNATURE-----

--Sig_/v+/ps58rm/ZJiF/KjnvaSr4--


From MAILER-DAEMON Mon Jul 09 14:40:59 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoItH-00083w-1I
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 14:40:59 -0400
Received: from eggs.gnu.org ([208.118.235.92]:46859)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoItB-0007up-QV
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:40:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoIt9-0001s7-OO
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:40:53 -0400
Received: from catbert.rellim.com ([204.17.205.1]:44767)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SoIt9-0001rl-1B
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 14:40:51 -0400
Received: from localhost (spidey.rellim.com [204.17.205.8])
	(authenticated bits=0)
	by catbert.rellim.com (8.14.5/8.14.5) with ESMTP id q69IekPm004922
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Mon, 9 Jul 2012 11:40:46 -0700
X-DKIM: OpenDKIM Filter v2.3.2 catbert.rellim.com q69IekPm004922
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert;
	t=1341859247; bh=yiWhUYlLErJCDgOMb6Ue8JvQSK9EiSb3IqjNuDqt2tM=;
	h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:
	Mime-Version:Content-Type;
	b=oT13rbWyESMo+jew+5biPiruDy0o8sKuIwdWd/54VtoOjJtrpPKH7RREtHfkexg7g
	Yp1yZEGWNJi1hwaffAsog==
Date: Mon, 9 Jul 2012 11:40:41 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: Chris Kuethe <chris.kuethe@gmail.com>
Message-ID: <20120709114041.731a1428.gem@rellim.com>
In-Reply-To: <CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
Organization: Rellim
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/3+YR/ztKH.E1yrL0dv3RgZz";
	protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 204.17.205.1
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:40:58 -0000

--Sig_/3+YR/ztKH.E1yrL0dv3RgZz
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Chris!

Apologies for answering you questions in reverse order.

On Mon, 9 Jul 2012 10:22:53 -0700
Chris Kuethe <chris.kuethe@gmail.com> wrote:

> A lazy search for "Garmin G1000 installation manual" doesn't give me
> any documentation on how to install one in an airplane. I bet there's
> a specification on where the receiver and antennas must be installed,
> and then a calibration screen for entering the specifics of that
> particular aircraft.

Nope, all it says it put the GPS antenna on the top and then casually
verify seemingly normal operation.  No calibration, just the RAIM.

On a transport category aircraft the height from wheels to antenna
will be added in by the Flight Management System (FMS).

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/3+YR/ztKH.E1yrL0dv3RgZz
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/7Ja0ACgkQBmnRqz71OvPYxQCgx2UOQnrLtCzeOQdeSCPUhqaW
a+YAoMe1EUnEiIG+h8UtsSfB1LOjGi8l
=Qaiz
-----END PGP SIGNATURE-----

--Sig_/3+YR/ztKH.E1yrL0dv3RgZz--


From MAILER-DAEMON Mon Jul 09 19:07:37 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoN3J-0000ZT-OL
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 19:07:37 -0400
Received: from eggs.gnu.org ([208.118.235.92]:36505)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <f96hajo@chalmers.se>) id 1SoN3H-0000ZN-H2
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 19:07:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <f96hajo@chalmers.se>) id 1SoN3F-0000XS-Rx
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 19:07:35 -0400
Received: from morinth.ita.chalmers.se ([129.16.226.169]:51084)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <f96hajo@chalmers.se>) id 1SoN3F-0000XM-LB
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 19:07:33 -0400
Received: from bridge1.fy.chalmers.se (129.16.110.161) by smtp.chalmers.se
	(129.16.10.240) with Microsoft SMTP Server (TLS) id 14.2.298.4;
	Tue, 10 Jul 2012 00:39:35 +0200
Date: Tue, 10 Jul 2012 00:39:27 +0200
From: =?ISO-8859-15?Q?H=E5kan_Johansson?= <f96hajo@chalmers.se>
X-X-Sender: htj@bridge1.fy.chalmers.se
To: Chris Kuethe <chris.kuethe@gmail.com>
In-Reply-To: <CAGHP0pLM7UpXPYo-L=8FN=Yq13SN04HWDB41jmo50WHBgcen-A@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1207100038240.73435@bridge1.fy.chalmers.se>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<CAGHP0pL7Puox-=N7x7e=NwsWyYPna6TPO0vhCP5JsVo+dcxSkw@mail.gmail.com>
	<CAENJYHo_2-0N=DoqO1CqfoXJQ8iCk19huhaMetqfPdQ_oKyf8A@mail.gmail.com>
	<CAGHP0p+YotsauSbcLg+ke58zx2=Ws34=NWBYfV0EFzyFQdwp_Q@mail.gmail.com>
	<CAENJYHobdFrhOg5dibkKoSOUEz-0VRkFa=+qubuLsMU1Yyt_MA@mail.gmail.com>
	<CAGHP0pLM7UpXPYo-L=8FN=Yq13SN04HWDB41jmo50WHBgcen-A@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="276930926-217012097-1341873575=:73435"
X-Originating-IP: [129.16.110.161]
X-detected-operating-system: by eggs.gnu.org: Windows XP/2000 (RFC1323+, w+,
	tstamp-)
X-Received-From: 129.16.226.169
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 23:07:36 -0000

--276930926-217012097-1341873575=:73435
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8BIT


On Mon, 9 Jul 2012, Chris Kuethe wrote:

> Yes, that's one approach. Be sure to consider:
> - surveyed positions of your fixed antennas
> - number of mobile devices
> - size of vessel
> - what happens under marginal signal conditions (do receivers claim to
> have a good quality fix but at the wrong position)
> - error detection/correction in the app
> - loop detection, so that this app does not use its own output like
> the output of a receiver.
> ...

Perhaps without the feeding-back path it would become simpler.  gpsd
provides data from individual devices, 'aggregate_gpsd' combines it into a
new feed.  Keeping the protocol format.  Clients can then connect to
aggregate_gpsd instead, should they want to.

Cheers,
Håkan


>
> web search for "gps attitude sensor" will give some hints on the
> current state of the art.
--276930926-217012097-1341873575=:73435--


From MAILER-DAEMON Mon Jul 09 23:46:45 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoRPR-00005l-SW
	for mharc-gpsd-dev@gnu.org; Mon, 09 Jul 2012 23:46:45 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39860)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <esr@golux>)
	id 1SoRPO-00005X-Ma
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 23:46:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@golux>) id 1SoRPM-0002zs-NU
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 23:46:42 -0400
Received: from 71-13-57-132.dhcp.bycy.mi.charter.com ([71.13.57.132]:56951
	helo=golux) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@golux>) id 1SoRPM-0002zj-Iz
	for gpsd-dev@nongnu.org; Mon, 09 Jul 2012 23:46:40 -0400
Received: by golux (Postfix, from userid 1000)
	id 2E31ABC7967; Mon,  9 Jul 2012 10:17:09 -0400 (EDT)
Date: Mon, 9 Jul 2012 10:17:09 -0400
From: Eric <esr@thyrsus.com>
To: Olivier Cornu <o.cornu@gmail.com>
Message-ID: <20120709141709.GA3402@thyrsus.com>
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.13.57.132
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 03:46:44 -0000

Olivier Cornu <o.cornu@gmail.com>:
> What did i expect? Put simply: more than basic multiplexing.
> I expected to gain something from device redundancy: either improved
> accuracy (reduced statistical error using several measures) or improved
> reliability (if one device starts behaving incorrectly), or both. It seems
> i get none.

That is correct.  The design philosophy of GPSD is that is intended to
pass through clean data identified by device.  The only postprocessing
we do is to compute velocities and error bars from the skyview
covariance matrix if the device doesn't report them.

This is a "mechanism, not policy" design.  You want to add a policy 
layer preferring a particular policy - merge and average.  Or maybe
merge and average after deciding to ignore a device that is "behaving
incorrectly". But what criterion are we to use to decide "incorrectly"?
That's another kind of policy.

There are several reasons not to go this route.  One is the very fact
that GPSD is designed to be a device multiplexer for multiple
applications - we can't know in advance that all applications using
the daemon at any given time will want the same policy.

Another is...if we add one policy, we'll immediately come under pressure
to add policy switches to enable lots of others. The code would bloat,
and there would be lots of new places for bugs to lurk.

Here is what I think you should do.  Pick a scripting language with
JSON support.  Write a proxy daemon that launches GPSD reporting to
a private port, reads the JSON from that, does whatever averaging
or other policy you want, and ships results to port 2947 as if it
were GPSD.  

I might be interested in carrying such a daemon in the distribution.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Tue Jul 10 02:23:34 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoTrC-0001UX-3l
	for mharc-gpsd-dev@gnu.org; Tue, 10 Jul 2012 02:23:34 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39063)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@hoegernet.de>) id 1SoTr8-0001UP-Se
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 02:23:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lists@hoegernet.de>) id 1SoTr6-0002nc-KR
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 02:23:30 -0400
Received: from mail.hoegergroup.de ([83.169.45.65]:50738)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@hoegernet.de>) id 1SoTr6-0002ms-B3
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 02:23:28 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.hoegergroup.de (Postfix) with ESMTP id 6C69016F00085
	for <gpsd-dev@nongnu.org>; Tue, 10 Jul 2012 08:23:24 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at hoegergroup.de
Received: from mail.hoegergroup.de ([127.0.0.1])
	by localhost (mail.hoegergroup.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WeiBHsh8w8XQ for <gpsd-dev@nongnu.org>;
	Tue, 10 Jul 2012 08:23:24 +0200 (CEST)
Received: from [10.10.10.37] (unknown [217.8.48.38])
	by mail.hoegergroup.de (Postfix) with ESMTPSA id 3CCA316F00077
	for <gpsd-dev@nongnu.org>; Tue, 10 Jul 2012 08:23:20 +0200 (CEST)
Message-ID: <4FFBCA58.9070700@hoegernet.de>
Date: Tue, 10 Jul 2012 08:23:20 +0200
From: =?ISO-8859-1?Q?Thorsten_H=F6ger?= <lists@hoegernet.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: gpsd-dev@nongnu.org
References: <CAFLV7-y9-Kv2bmMwHfjqOagDtd2ch1b6+r_pgYzydhjwmRrxcQ@mail.gmail.com>
	<20120709141709.GA3402@thyrsus.com>
In-Reply-To: <20120709141709.GA3402@thyrsus.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 83.169.45.65
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 06:23:32 -0000

Hi,

a collegue wrote his thesis on this topic.
It was called Smart GPS.

He describes some mathematical models to merge GPS sources.

You can find it under this link but it is only available in German.
http://elib.uni-stuttgart.de/opus/volltexte/2009/4023/index.html

Regards,
Thorsten

Am 09.07.2012 16:17, schrieb Eric:
> Olivier Cornu <o.cornu@gmail.com>:
>> What did i expect? Put simply: more than basic multiplexing.
>> I expected to gain something from device redundancy: either improved
>> accuracy (reduced statistical error using several measures) or improved
>> reliability (if one device starts behaving incorrectly), or both. It seems
>> i get none.
> That is correct.  The design philosophy of GPSD is that is intended to
> pass through clean data identified by device.  The only postprocessing
> we do is to compute velocities and error bars from the skyview
> covariance matrix if the device doesn't report them.
>
> This is a "mechanism, not policy" design.  You want to add a policy 
> layer preferring a particular policy - merge and average.  Or maybe
> merge and average after deciding to ignore a device that is "behaving
> incorrectly". But what criterion are we to use to decide "incorrectly"?
> That's another kind of policy.
>
> There are several reasons not to go this route.  One is the very fact
> that GPSD is designed to be a device multiplexer for multiple
> applications - we can't know in advance that all applications using
> the daemon at any given time will want the same policy.
>
> Another is...if we add one policy, we'll immediately come under pressure
> to add policy switches to enable lots of others. The code would bloat,
> and there would be lots of new places for bugs to lurk.
>
> Here is what I think you should do.  Pick a scripting language with
> JSON support.  Write a proxy daemon that launches GPSD reporting to
> a private port, reads the JSON from that, does whatever averaging
> or other policy you want, and ships results to port 2947 as if it
> were GPSD.  
>
> I might be interested in carrying such a daemon in the distribution.




From MAILER-DAEMON Tue Jul 10 04:49:44 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoW8e-0006rs-Dg
	for mharc-gpsd-dev@gnu.org; Tue, 10 Jul 2012 04:49:44 -0400
Received: from eggs.gnu.org ([208.118.235.92]:57934)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SoW8b-0006rb-8a
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 04:49:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SoW8Y-0004C2-B7
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 04:49:40 -0400
Received: from mailout08.t-online.de ([194.25.134.20]:41283)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SoW8X-0004BL-U0
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 04:49:38 -0400
Received: from fwd02.aul.t-online.de (fwd02.aul.t-online.de )
	by mailout08.t-online.de with smtp 
	id 1SoW8T-0000hY-S1; Tue, 10 Jul 2012 10:49:33 +0200
Received: from localhost
	(bRCgb0ZvwhO2qPFo3FxEqJhDH8aeKCkEdLa8SOVCk8qLFPtDV-ME14PBfVOWNragyM@[172.20.101.250])
	by fwd02.aul.t-online.de
	with esmtp id 1SoW8R-0wTutM0; Tue, 10 Jul 2012 10:49:31 +0200
MIME-Version: 1.0
Received: from 93.218.117.186:41921 by cmpweb46.aul.t-online.de with
	HTTP/1.1 (NGCS V4-0-6-1 on API V3-11-12-2)
In-Reply-To: <20120709141709.GA3402@thyrsus.com>
References: <20120709141709.GA3402@thyrsus.com>
Date: Tue, 10 Jul 2012 10:49:31 +0200
To: esr@thyrsus.com, "Olivier Cornu" <o.cornu@gmail.com>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-1
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: multipart/alternative;
	boundary="=_028026651f27697091736a07386d7216"
Message-ID: <1SoW8R-0wTutM0@fwd02.aul.t-online.de>
X-ID: bRCgb0ZvwhO2qPFo3FxEqJhDH8aeKCkEdLa8SOVCk8qLFPtDV-ME14PBfVOWNragyM@t-dialin.net
X-TOI-MSGID: 7cfbf508-100a-4d14-a85b-2314f42f030c
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.20
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev]
 =?utf-8?q?Using_multiple_location_sources_to_improve_a?=
 =?utf-8?q?ccuracy_and_reliability?=
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 08:49:43 -0000

--=_028026651f27697091736a07386d7216
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hello, 

	if you have more then one source of the position, the idea is obvious
to merge them into one position, as most of the gpsd aware
applications expect only one position source. 

	For me the point is, that there is already so much code in gpsd that
address the needs of only very few people, and this options need
difficult configuration, and it may be implemented in so many
different ways. 

	Perhaps it is time to consider a plugin interface to keep gpsd lean,
to fulfill special needs, and to avoid multiple coding. 

	Reinhard 

	-----Original-Nachricht----- 

	Von: Eric <esr@thyrsus.com> 

	An: Olivier Cornu <o.cornu@gmail.com> 

	Cc: gpsd-dev@nongnu.org 

	Betreff: Re: [gpsd-dev] Using multiple location sources to improve
accuracy and reliability 

	Datum: Mon, 09 Jul 2012 16:17:09 +0200 

	Olivier Cornu <o.cornu@gmail.com>: 

	> What did i expect? Put simply: more than basic multiplexing. 

	> I expected to gain something from device redundancy: either
improved 

	> accuracy (reduced statistical error using several measures) or
improved 

	> reliability (if one device starts behaving incorrectly), or both.
It seems 

	> i get none. 

	That is correct.  The design philosophy of GPSD is that is intended
to 

	pass through clean data identified by device.  The only
postprocessing 

	we do is to compute velocities and error bars from the skyview 

	covariance matrix if the device doesn't report them. 

	This is a "mechanism, not policy" design.  You want to add a policy 

	layer preferring a particular policy - merge and average.  Or maybe 

	merge and average after deciding to ignore a device that is "behaving


	incorrectly". But what criterion are we to use to decide
"incorrectly"? 

	That's another kind of policy. 

	There are several reasons not to go this route.  One is the very fact


	that GPSD is designed to be a device multiplexer for multiple 

	applications - we can't know in advance that all applications using 

	the daemon at any given time will want the same policy. 

	Another is...if we add one policy, we'll immediately come under
pressure 

	to add policy switches to enable lots of others. The code would
bloat, 

	and there would be lots of new places for bugs to lurk. 

	Here is what I think you should do.  Pick a scripting language with 

	JSON support.  Write a proxy daemon that launches GPSD reporting to 

	a private port, reads the JSON from that, does whatever averaging 

	or other policy you want, and ships results to port 2947 as if it 

	were GPSD. 

	I might be interested in carrying such a daemon in the distribution. 

	-- 

	<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
--=_028026651f27697091736a07386d7216
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><title></title><meta http-equiv=3D"Content-Type" content=3D"tex=
t/html; charset=3DUTF-8"/></head><body><p style=3D"margin: 0px;">Hello,</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">if you have more then one source of the position,=
 the idea is obvious to merge them into one position, as most of the gpsd a=
ware applications expect only one position source.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">For me the point is, that there is already so muc=
h code in gpsd that address the needs of only very few people, and this opt=
ions need difficult configuration, and it may be implemented in so many&nbs=
p;different ways.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Perhaps it is time to consider a plugin interface=
 to keep gpsd lean, to fulfill special needs, and to avoid multiple coding.=
</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Reinhard</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">-----Original-Nachricht-----</p>
<p style=3D"margin: 0px;">Von: Eric &lt;esr@thyrsus.com&gt;</p>
<p style=3D"margin: 0px;">An: Olivier Cornu &lt;o.cornu@gmail.com&gt;</p>
<p style=3D"margin: 0px;">Cc: gpsd-dev@nongnu.org</p>
<p style=3D"margin: 0px;">Betreff: Re: [gpsd-dev] Using multiple location s=
ources to improve accuracy and reliability</p>
<p style=3D"margin: 0px;">Datum: Mon, 09 Jul 2012 16:17:09 +0200</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Olivier Cornu &lt;o.cornu@gmail.com&gt;:</p>
<p style=3D"margin: 0px;">&gt; What did i expect? Put simply: more than bas=
ic multiplexing.</p>
<p style=3D"margin: 0px;">&gt; I expected to gain something from device red=
undancy: either improved</p>
<p style=3D"margin: 0px;">&gt; accuracy (reduced statistical error using se=
veral measures) or improved</p>
<p style=3D"margin: 0px;">&gt; reliability (if one device starts behaving i=
ncorrectly), or both. It seems</p>
<p style=3D"margin: 0px;">&gt; i get none.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">That is correct.  The design philosophy of GPSD i=
s that is intended to</p>
<p style=3D"margin: 0px;">pass through clean data identified by device.  Th=
e only postprocessing</p>
<p style=3D"margin: 0px;">we do is to compute velocities and error bars fro=
m the skyview</p>
<p style=3D"margin: 0px;">covariance matrix if the device doesn't report th=
em.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">This is a "mechanism, not policy" design.  You wa=
nt to add a policy</p>
<p style=3D"margin: 0px;">layer preferring a particular policy - merge and =
average.  Or maybe</p>
<p style=3D"margin: 0px;">merge and average after deciding to ignore a devi=
ce that is "behaving</p>
<p style=3D"margin: 0px;">incorrectly". But what criterion are we to use to=
 decide "incorrectly"?</p>
<p style=3D"margin: 0px;">That's another kind of policy.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">There are several reasons not to go this route.  =
One is the very fact</p>
<p style=3D"margin: 0px;">that GPSD is designed to be a device multiplexer =
for multiple</p>
<p style=3D"margin: 0px;">applications - we can't know in advance that all =
applications using</p>
<p style=3D"margin: 0px;">the daemon at any given time will want the same p=
olicy.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Another is...if we add one policy, we'll immediat=
ely come under pressure</p>
<p style=3D"margin: 0px;">to add policy switches to enable lots of others. =
The code would bloat,</p>
<p style=3D"margin: 0px;">and there would be lots of new places for bugs to=
 lurk.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Here is what I think you should do.  Pick a scrip=
ting language with</p>
<p style=3D"margin: 0px;">JSON support.  Write a proxy daemon that launches=
 GPSD reporting to</p>
<p style=3D"margin: 0px;">a private port, reads the JSON from that, does wh=
atever averaging</p>
<p style=3D"margin: 0px;">or other policy you want, and ships results to po=
rt 2947 as if it</p>
<p style=3D"margin: 0px;">were GPSD.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">I might be interested in carrying such a daemon i=
n the distribution.</p>
<p style=3D"margin: 0px;">--</p>
<p style=3D"margin: 0px;">&lt;a href=3D"http://www.catb.org/~esr/"&gt;Eric =
S. Raymond&lt;/a&gt;</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">&nbsp;</p></body></html>
--=_028026651f27697091736a07386d7216--




From MAILER-DAEMON Tue Jul 10 06:30:05 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SoXhl-0005vt-Gu
	for mharc-gpsd-dev@gnu.org; Tue, 10 Jul 2012 06:30:05 -0400
Received: from eggs.gnu.org ([208.118.235.92]:59797)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jon.schlueter@gmail.com>) id 1SoXhe-0005tQ-Or
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 06:30:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jon.schlueter@gmail.com>) id 1SoXhY-00077k-J7
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 06:29:58 -0400
Received: from mail-vc0-f173.google.com ([209.85.220.173]:63450)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jon.schlueter@gmail.com>) id 1SoXhY-00076g-CS
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 06:29:52 -0400
Received: by vcbfo13 with SMTP id fo13so8409097vcb.4
	for <gpsd-dev@nongnu.org>; Tue, 10 Jul 2012 03:29:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=ELZRgnpiQz+VaZ0dh/OAyMGQvpuOarUD6tZYhzmoMoY=;
	b=pCUVmxupj66OoNO6ZtWhhZkiU1E0XXFjK/6SOiJFLZNwF0hXSXRQ8WCagkXf+ZM+w2
	QvGDyV8bqOeJdMZfqhh3vfsbKtSOwZiRLklzaYgAYEqWrKm4HXPXJI9tAx7nGYNB6I3Q
	JOfrM3iVyjxHCovlbbVDfmQYmrn2qMVFAActY2A8WzKE2qROU5kZG3cd8d4a8TRIVZ2O
	10cFsIrcDlNWN9ZcKMlYFAraCd6jmQI7mMtewvas6BnEoWt7mfByk7ZkGwKmey38R5+J
	mMW7Hn/907FkHuMO+pg1J7uyZntNxQnByOj8PfVwM1FTWYaIPGthgmyVnNbb2pFbD47W
	LTjQ==
MIME-Version: 1.0
Received: by 10.52.64.146 with SMTP id o18mr1248045vds.55.1341916189787; Tue,
	10 Jul 2012 03:29:49 -0700 (PDT)
Received: by 10.220.14.21 with HTTP; Tue, 10 Jul 2012 03:29:49 -0700 (PDT)
In-Reply-To: <1SoW8R-0wTutM0@fwd02.aul.t-online.de>
References: <20120709141709.GA3402@thyrsus.com>
	<1SoW8R-0wTutM0@fwd02.aul.t-online.de>
Date: Tue, 10 Jul 2012 06:29:49 -0400
Message-ID: <CAOSy7+_2oA-q+JMh8V20F6zvsdr80A=B6zain_NXKyutf+sVxw@mail.gmail.com>
From: Jon Schlueter <jon.schlueter@gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.220.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 10:30:04 -0000

> Perhaps it is time to consider a plugin interface to keep gpsd lean, to
> fulfill special needs, and to avoid multiple coding.

The Daemon implementation that ESR referred to would be something
along those lines.
Scripting languages seem to be pretty good at massaging data around
and prototyping an idea together.  When you get something like that
together at least good enough for your usage then there are probably
more ideas that can be built off of it.

Jon


From MAILER-DAEMON Tue Jul 10 15:19:55 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SofyV-0003Sm-U9
	for mharc-gpsd-dev@gnu.org; Tue, 10 Jul 2012 15:19:55 -0400
Received: from eggs.gnu.org ([208.118.235.92]:48779)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SofyU-0003SO-0Q
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 15:19:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SofyO-0002rX-Eg
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 15:19:53 -0400
Received: from catbert.rellim.com ([204.17.205.1]:60801)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1SofyN-0002qA-UD
	for gpsd-dev@nongnu.org; Tue, 10 Jul 2012 15:19:48 -0400
Received: from localhost (spidey.rellim.com [204.17.205.8])
	(authenticated bits=0)
	by catbert.rellim.com (8.14.5/8.14.5) with ESMTP id q6AJJUlF012642
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Tue, 10 Jul 2012 12:19:30 -0700
X-DKIM: OpenDKIM Filter v2.3.2 catbert.rellim.com q6AJJUlF012642
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert;
	t=1341947970; bh=quC1Rrk+Jt8PHB4rLO7L+TwFKBsqVd5Ewl1ZnK/aA+0=;
	h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:
	Mime-Version:Content-Type;
	b=t5HoP94r8etF6QdqRe4lPomYkv9EIKcl8TyFXe2J+rVmDpc02wmp0taNi/b2brdxe
	gEeul0yjLWNhYp9JBp/MA==
Date: Tue, 10 Jul 2012 12:19:25 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Message-ID: <20120710121925.547b13b5.gem@rellim.com>
In-Reply-To: <1SoW8R-0wTutM0@fwd02.aul.t-online.de>
References: <20120709141709.GA3402@thyrsus.com>
	<1SoW8R-0wTutM0@fwd02.aul.t-online.de>
Organization: Rellim
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/qvFeK+fV_9Bos8QTWW24T9=";
	protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 204.17.205.1
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 19:19:55 -0000

--Sig_/qvFeK+fV_9Bos8QTWW24T9=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Reinhard.Arlt@t-online.de!

On Tue, 10 Jul 2012 10:49:31 +0200
"Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de> wrote:

>=20
> 	if you have more then one source of the position, the idea is
> obvious to merge them into one position, as most of the gpsd aware
> applications expect only one position source.=20

Which is analogous to how an FMS in a large aircraft merges the INS,
VOR, GPS, ILS position data into a best guess fix.

> 	For me the point is, that there is already so much code in
> gpsd that address the needs of only very few people, and this options
> need difficult configuration, and it may be implemented in so many
> different ways.=20

Yup.

> 	Perhaps it is time to consider a plugin interface to keep
> gpsd lean, to fulfill special needs, and to avoid multiple coding.=20

I would lean against that.  Plugins create another interface that
must be documented and maintained, when we already have a very nice
interface for consumers of the gpsd data that also carries all the
data a post processor needs from gpsd.

I lean towards the shim daemon approach already mentioned by Eric.  That
is the linux way, keep each module focused on the one task it does best.
A plugin architecture also seriously contrains how any plugin must be
written without providing any synergy.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/qvFeK+fV_9Bos8QTWW24T9=
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/8gEEACgkQBmnRqz71OvN2wQCggTs0kWWl1fB5dxrTFx29xazb
7nMAoLUWtxIC/a7hQmyNlCbhLtJUH3k2
=+7Yo
-----END PGP SIGNATURE-----

--Sig_/qvFeK+fV_9Bos8QTWW24T9=--


From MAILER-DAEMON Thu Jul 12 08:50:05 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SpIqL-0002PJ-PO
	for mharc-gpsd-dev@gnu.org; Thu, 12 Jul 2012 08:50:05 -0400
Received: from eggs.gnu.org ([208.118.235.92]:44389)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpIqD-0002Mz-KO
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 08:50:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpIq9-0001Rl-3Q
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 08:49:57 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:40591)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpIq8-0001Rb-Uu
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 08:49:53 -0400
Received: by yenl1 with SMTP id l1so2559857yen.4
	for <gpsd-dev@nongnu.org>; Thu, 12 Jul 2012 05:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=73QTv5bEWBsZQfdQ7QjzsUgKXVQD8/ApMHaQMZeiddU=;
	b=bsl8Dezr+9ISX0lHG/sIXPH7BTmaBb6DmmstbM2ajCfD1QZKKe6G2B9Mtpevf+UuVG
	R/mMUMFfo0uu7Kydd38YKRGvA9HI3bwBVVVc0Zy97/qMn5VqY2QYAxH3LQsM8nfKQBJC
	M5IsphXjDzVtkvDv/5gzCTrVWwCenIi69smhgo2wFcu3EquLLpwC1GX2c7FSIFr2ace0
	fCMVj1O6Ov7UdzFMRP16REmAsHuUDDKCHl2XcmjdRodlJU9kNReaHlOUCBzhDdlDMjSf
	SHZucXaah5AifJIMCUGU0wM646bN2bpmXMxpBaA/XDQ55oT+8R+dFpfHxtO4gcMZg1KK
	yZKA==
Received: by 10.101.176.35 with SMTP id d35mr17948401anp.59.1342097392298;
	Thu, 12 Jul 2012 05:49:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Thu, 12 Jul 2012 05:49:32 -0700 (PDT)
From: Olivier Cornu <o.cornu@gmail.com>
Date: Thu, 12 Jul 2012 14:49:32 +0200
Message-ID: <CAFLV7-ztEePCh1RRd7hwApY+9kKoonOupMWjJt_Chu-it8q39w@mail.gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.173
Subject: [gpsd-dev] Virtual devices (as a solution to multiple sources
	location)
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 12:50:03 -0000

Thanks everyone for the feedback, comments and suggestions.
There seem to be some interest in harvesting multi-source capabilities
even if there is no consensus yet on how such code should work or
where it would belong.

What do we agree on?
- We all agree that such capabilities are, as Eric mentioned, "policy
driven": they go beyond the mechanical multiplexing gpsd has been
devoting itself to so far.
- We agree that multi-source capabilities are powerful, already used
in real-life critical environments like aeronautics as Gary noted, and
can get much smarter (see Thornston's link) than the basic stuff i
have in mind for my own use.
- We also seem to agree that such policies will require flexibility in
the code to accommodate to particular use cases, as Chris (config
settings) and Reinhard (policy plugins) suggested.
- Hopefully, we agree that as location technologies become ubiquitous
and diverse, multiple location sensors are becoming the default setup,
thus there should soon be a "policy layer" hub (or compound location
provider) to get the most out of it.

I would advocate that there is much (market) value in being the
default location provider for a platform.
I believe gpsd already is the default location provider on open
platforms, although it perhaps only sees itself as a GPS multiplexer.
Because it's the last layer clients talk to, and most clients
rightfully expect all the dirty location job is done at this point
(they expect one clean location). That's why i expected more than
multiplexing when i plugged my second device, and i should know
better: contrary to most users, i peeked and poked into gpsd code
already.
I would advocate that most users would expect this stuff to be somehow
part of gpsd as well. And i believe we could add it to gpsd without
compromising the mechanical multiplexing it does right.


To make things simpler, we can see this policy layer as functionally
distinct from the mechanical multiplexing gpsd does. It is thus
tempting to push it back in its own daemon.
However, if we look closer, both layers have some tight links that
will be hard to stretch that much. Timing issues (when computing a
single position from asynchronous location speakers), definition of a
3D fix (takes one more satellite in aeronautics), raw device state
knowledge and control (ability to detect and right to shut down a
device in case of incorrect behaviour), and probably more.
They also have a lot in common. Frankly, if i needed to average
locations for my own use i'd just add 3 lines to consume_packets(); I
wouldn't code a whole gpsd proxy for that, be it in python.
Anyway, i think it makes sense to talk about the policy layer in terms
of the current gpsd architecture, no matter where it ends up (library
or daemon).


As i see it, we just need virtual devices.
Basically, virtual devices are like real devices: they have their own
driver (implementing policy) and spit their own stream of JSON
location events for client apps.
But virtual devices are also local clients, as they subscribe and
consume real devices output.
Finally, virtual devices have a little bit of their own interaction
with gpsd (if they can shut down/reboot a device, for example).

Let's take a simple example: the /dev/aero/ttyUSB0 virtual device,
which provides the very same streams /dev/ttyUSB0 provides, except
that it needs one more satellite to call it a 3D fix.
I like this example because it's not even a compound sources provider,
yet it makes perfect sense as a policy.

The good point here is that we'd piggyback on existing gpsd paradigm,
interfaces and well-tested code. The remaining code could be
conditioned to a precompiler switch.
Let's not fool ourselves: even though there's a need for flexibility
(drivers) and possibilities are infinite, what we'd probably end up
with is just a few virtual device drivers that make 95% of gpsd users
happy. Location sources redundancy is no different than, say,
hard-drive redundancy (the set of original efficient strategies is
small).
Overall, i believe it would be a reasonably small addition relatively
to gpsd current size.


Looking forward to your comments.

--
Olivier Cornu


From MAILER-DAEMON Thu Jul 12 10:35:46 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SpKUb-0005Un-VN
	for mharc-gpsd-dev@gnu.org; Thu, 12 Jul 2012 10:35:46 -0400
Received: from eggs.gnu.org ([208.118.235.92]:46072)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpKUQ-0005LO-Ap
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 10:35:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpKUO-0007MH-H9
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 10:35:34 -0400
Received: from mailout05.t-online.de ([194.25.134.82]:41946)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpKUO-0007Ly-1H
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 10:35:32 -0400
Received: from fwd23.aul.t-online.de (fwd23.aul.t-online.de )
	by mailout05.t-online.de with smtp 
	id 1SpKUL-00049p-5n; Thu, 12 Jul 2012 16:35:29 +0200
Received: from localhost
	(bKpu4+ZcohBGkdqsf-nvVsnqgDjwXjzFv7cKZVecoTOVbS+BQ0YxdtxHLDwJW0rgho@[172.20.101.250])
	by fwd23.aul.t-online.de
	with esmtp id 1SpKUA-0MjYhM0; Thu, 12 Jul 2012 16:35:18 +0200
MIME-Version: 1.0
Received: from 89.183.38.14:58656 by cmpweb62.aul.t-online.de with HTTP/1.1
	(NGCS V4-0-6-1 on API V3-11-12-2)
In-Reply-To: <CAFLV7-ztEePCh1RRd7hwApY+9kKoonOupMWjJt_Chu-it8q39w@mail.gmail.com>
References: <CAFLV7-ztEePCh1RRd7hwApY+9kKoonOupMWjJt_Chu-it8q39w@mail.gmail.com>
Date: Thu, 12 Jul 2012 16:35:18 +0200
To: "Olivier Cornu" <o.cornu@gmail.com>, gpsd-dev@nongnu.org
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-1
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: multipart/alternative;
	boundary="=_8eadec307a2a9fe89f93b7889a20125c"
Message-ID: <1SpKUA-0MjYhM0@fwd23.aul.t-online.de>
X-ID: bKpu4+ZcohBGkdqsf-nvVsnqgDjwXjzFv7cKZVecoTOVbS+BQ0YxdtxHLDwJW0rgho@t-dialin.net
X-TOI-MSGID: 9982b084-ba81-4c41-8051-75819b12bc0b
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.82
Subject: Re: [gpsd-dev]
 =?utf-8?q?Virtual_devices_=28as_a_solution_to_multiple?=
 =?utf-8?q?_sources_location=29?=
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 14:35:44 -0000

--=_8eadec307a2a9fe89f93b7889a20125c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hallo, 

	for a quick solution, Eric suggestion would be for me the way to go. 

	I would prefer to code it in "C". 

	I have considered such a solution too, but i had to concentrate on
the nmea2000 code and test bench at the moment. 

	For me, it is not clear, how the daemon, that merge the data, can
select the specific position sources with its gps_open() call. 

	If you connect only the position sources to the first gpsd, and all
other sensors to the second, all should be fine, 

	but for a nmea2000 system, i can not do this, so here all unneeded
messages from other sensors has be forwarded by the 

	intermediate daemon. 

	Reinhard 

	-----Original-Nachricht----- 

	Von: Olivier Cornu <o.cornu@gmail.com> 

	An: gpsd-dev@nongnu.org 

	Betreff: [gpsd-dev] Virtual devices (as a solution to multiple
sources location) 

	Datum: Thu, 12 Jul 2012 14:49:32 +0200 

	Thanks everyone for the feedback, comments and suggestions. 

	There seem to be some interest in harvesting multi-source
capabilities 

	even if there is no consensus yet on how such code should work or 

	where it would belong. 

	What do we agree on? 

	- We all agree that such capabilities are, as Eric mentioned, "policy


	driven": they go beyond the mechanical multiplexing gpsd has been 

	devoting itself to so far. 

	- We agree that multi-source capabilities are powerful, already used 

	in real-life critical environments like aeronautics as Gary noted,
and 

	can get much smarter (see Thornston's link) than the basic stuff i 

	have in mind for my own use. 

	- We also seem to agree that such policies will require flexibility
in 

	the code to accommodate to particular use cases, as Chris (config 

	settings) and Reinhard (policy plugins) suggested. 

	- Hopefully, we agree that as location technologies become ubiquitous


	and diverse, multiple location sensors are becoming the default
setup, 

	thus there should soon be a "policy layer" hub (or compound location 

	provider) to get the most out of it. 

	I would advocate that there is much (market) value in being the 

	default location provider for a platform. 

	I believe gpsd already is the default location provider on open 

	platforms, although it perhaps only sees itself as a GPS multiplexer.


	Because it's the last layer clients talk to, and most clients 

	rightfully expect all the dirty location job is done at this point 

	(they expect one clean location). That's why i expected more than 

	multiplexing when i plugged my second device, and i should know 

	better: contrary to most users, i peeked and poked into gpsd code 

	already. 

	I would advocate that most users would expect this stuff to be
somehow 

	part of gpsd as well. And i believe we could add it to gpsd without 

	compromising the mechanical multiplexing it does right. 

	To make things simpler, we can see this policy layer as functionally 

	distinct from the mechanical multiplexing gpsd does. It is thus 

	tempting to push it back in its own daemon. 

	However, if we look closer, both layers have some tight links that 

	will be hard to stretch that much. Timing issues (when computing a 

	single position from asynchronous location speakers), definition of a


	3D fix (takes one more satellite in aeronautics), raw device state 

	knowledge and control (ability to detect and right to shut down a 

	device in case of incorrect behaviour), and probably more. 

	They also have a lot in common. Frankly, if i needed to average 

	locations for my own use i'd just add 3 lines to consume_packets(); I


	wouldn't code a whole gpsd proxy for that, be it in python. 

	Anyway, i think it makes sense to talk about the policy layer in
terms 

	of the current gpsd architecture, no matter where it ends up (library


	or daemon). 

	As i see it, we just need virtual devices. 

	Basically, virtual devices are like real devices: they have their own


	driver (implementing policy) and spit their own stream of JSON 

	location events for client apps. 

	But virtual devices are also local clients, as they subscribe and 

	consume real devices output. 

	Finally, virtual devices have a little bit of their own interaction 

	with gpsd (if they can shut down/reboot a device, for example). 

	Let's take a simple example: the /dev/aero/ttyUSB0 virtual device, 

	which provides the very same streams /dev/ttyUSB0 provides, except 

	that it needs one more satellite to call it a 3D fix. 

	I like this example because it's not even a compound sources
provider, 

	yet it makes perfect sense as a policy. 

	The good point here is that we'd piggyback on existing gpsd paradigm,


	interfaces and well-tested code. The remaining code could be 

	conditioned to a precompiler switch. 

	Let's not fool ourselves: even though there's a need for flexibility 

	(drivers) and possibilities are infinite, what we'd probably end up 

	with is just a few virtual device drivers that make 95% of gpsd users


	happy. Location sources redundancy is no different than, say, 

	hard-drive redundancy (the set of original efficient strategies is 

	small). 

	Overall, i believe it would be a reasonably small addition relatively


	to gpsd current size. 

	Looking forward to your comments. 

	-- 

	Olivier Cornu
--=_8eadec307a2a9fe89f93b7889a20125c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><title></title><meta http-equiv=3D"Content-Type" content=3D"tex=
t/html; charset=3DUTF-8"/></head><body><p style=3D"margin: 0px;">Hallo,</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">for a quick solution, Eric suggestion would be fo=
r me the way to go.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">I would prefer to code it in "C".</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">I have considered such a solution too, but i had =
to concentrate on the nmea2000 code and test bench at the moment.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">For me, it is not clear, how the daemon, that mer=
ge the data, can select the specific position sources with its gps_open() c=
all.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">If you connect only the position sources to the f=
irst gpsd, and all other sensors to the second, all should be fine,</p>
<p style=3D"margin: 0px;">but for a nmea2000 system, i can not do this, so =
here all unneeded messages from other sensors has be forwarded by the</p>
<p style=3D"margin: 0px;">intermediate daemon.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Reinhard</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">-----Original-Nachricht-----</p>
<p style=3D"margin: 0px;">Von: Olivier Cornu &lt;o.cornu@gmail.com&gt;</p>
<p style=3D"margin: 0px;">An: gpsd-dev@nongnu.org</p>
<p style=3D"margin: 0px;">Betreff: [gpsd-dev] Virtual devices (as a solutio=
n to multiple sources location)</p>
<p style=3D"margin: 0px;">Datum: Thu, 12 Jul 2012 14:49:32 +0200</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Thanks everyone for the feedback, comments and su=
ggestions.</p>
<p style=3D"margin: 0px;">There seem to be some interest in harvesting mult=
i-source capabilities</p>
<p style=3D"margin: 0px;">even if there is no consensus yet on how such cod=
e should work or</p>
<p style=3D"margin: 0px;">where it would belong.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">What do we agree on?</p>
<p style=3D"margin: 0px;">- We all agree that such capabilities are, as Eri=
c mentioned, "policy</p>
<p style=3D"margin: 0px;">driven": they go beyond the mechanical multiplexi=
ng gpsd has been</p>
<p style=3D"margin: 0px;">devoting itself to so far.</p>
<p style=3D"margin: 0px;">- We agree that multi-source capabilities are pow=
erful, already used</p>
<p style=3D"margin: 0px;">in real-life critical environments like aeronauti=
cs as Gary noted, and</p>
<p style=3D"margin: 0px;">can get much smarter (see Thornston's link) than =
the basic stuff i</p>
<p style=3D"margin: 0px;">have in mind for my own use.</p>
<p style=3D"margin: 0px;">- We also seem to agree that such policies will r=
equire flexibility in</p>
<p style=3D"margin: 0px;">the code to accommodate to particular use cases, =
as Chris (config</p>
<p style=3D"margin: 0px;">settings) and Reinhard (policy plugins) suggested=
.</p>
<p style=3D"margin: 0px;">- Hopefully, we agree that as location technologi=
es become ubiquitous</p>
<p style=3D"margin: 0px;">and diverse, multiple location sensors are becomi=
ng the default setup,</p>
<p style=3D"margin: 0px;">thus there should soon be a "policy layer" hub (o=
r compound location</p>
<p style=3D"margin: 0px;">provider) to get the most out of it.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">I would advocate that there is much (market) valu=
e in being the</p>
<p style=3D"margin: 0px;">default location provider for a platform.</p>
<p style=3D"margin: 0px;">I believe gpsd already is the default location pr=
ovider on open</p>
<p style=3D"margin: 0px;">platforms, although it perhaps only sees itself a=
s a GPS multiplexer.</p>
<p style=3D"margin: 0px;">Because it's the last layer clients talk to, and =
most clients</p>
<p style=3D"margin: 0px;">rightfully expect all the dirty location job is d=
one at this point</p>
<p style=3D"margin: 0px;">(they expect one clean location). That's why i ex=
pected more than</p>
<p style=3D"margin: 0px;">multiplexing when i plugged my second device, and=
 i should know</p>
<p style=3D"margin: 0px;">better: contrary to most users, i peeked and poke=
d into gpsd code</p>
<p style=3D"margin: 0px;">already.</p>
<p style=3D"margin: 0px;">I would advocate that most users would expect thi=
s stuff to be somehow</p>
<p style=3D"margin: 0px;">part of gpsd as well. And i believe we could add =
it to gpsd without</p>
<p style=3D"margin: 0px;">compromising the mechanical multiplexing it does =
right.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">To make things simpler, we can see this policy la=
yer as functionally</p>
<p style=3D"margin: 0px;">distinct from the mechanical multiplexing gpsd do=
es. It is thus</p>
<p style=3D"margin: 0px;">tempting to push it back in its own daemon.</p>
<p style=3D"margin: 0px;">However, if we look closer, both layers have some=
 tight links that</p>
<p style=3D"margin: 0px;">will be hard to stretch that much. Timing issues =
(when computing a</p>
<p style=3D"margin: 0px;">single position from asynchronous location speake=
rs), definition of a</p>
<p style=3D"margin: 0px;">3D fix (takes one more satellite in aeronautics),=
 raw device state</p>
<p style=3D"margin: 0px;">knowledge and control (ability to detect and righ=
t to shut down a</p>
<p style=3D"margin: 0px;">device in case of incorrect behaviour), and proba=
bly more.</p>
<p style=3D"margin: 0px;">They also have a lot in common. Frankly, if i nee=
ded to average</p>
<p style=3D"margin: 0px;">locations for my own use i'd just add 3 lines to =
consume_packets(); I</p>
<p style=3D"margin: 0px;">wouldn't code a whole gpsd proxy for that, be it =
in python.</p>
<p style=3D"margin: 0px;">Anyway, i think it makes sense to talk about the =
policy layer in terms</p>
<p style=3D"margin: 0px;">of the current gpsd architecture, no matter where=
 it ends up (library</p>
<p style=3D"margin: 0px;">or daemon).</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">As i see it, we just need virtual devices.</p>
<p style=3D"margin: 0px;">Basically, virtual devices are like real devices:=
 they have their own</p>
<p style=3D"margin: 0px;">driver (implementing policy) and spit their own s=
tream of JSON</p>
<p style=3D"margin: 0px;">location events for client apps.</p>
<p style=3D"margin: 0px;">But virtual devices are also local clients, as th=
ey subscribe and</p>
<p style=3D"margin: 0px;">consume real devices output.</p>
<p style=3D"margin: 0px;">Finally, virtual devices have a little bit of the=
ir own interaction</p>
<p style=3D"margin: 0px;">with gpsd (if they can shut down/reboot a device,=
 for example).</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Let's take a simple example: the /dev/aero/ttyUSB=
0 virtual device,</p>
<p style=3D"margin: 0px;">which provides the very same streams /dev/ttyUSB0=
 provides, except</p>
<p style=3D"margin: 0px;">that it needs one more satellite to call it a 3D =
fix.</p>
<p style=3D"margin: 0px;">I like this example because it's not even a compo=
und sources provider,</p>
<p style=3D"margin: 0px;">yet it makes perfect sense as a policy.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">The good point here is that we'd piggyback on exi=
sting gpsd paradigm,</p>
<p style=3D"margin: 0px;">interfaces and well-tested code. The remaining co=
de could be</p>
<p style=3D"margin: 0px;">conditioned to a precompiler switch.</p>
<p style=3D"margin: 0px;">Let's not fool ourselves: even though there's a n=
eed for flexibility</p>
<p style=3D"margin: 0px;">(drivers) and possibilities are infinite, what we=
'd probably end up</p>
<p style=3D"margin: 0px;">with is just a few virtual device drivers that ma=
ke 95% of gpsd users</p>
<p style=3D"margin: 0px;">happy. Location sources redundancy is no differen=
t than, say,</p>
<p style=3D"margin: 0px;">hard-drive redundancy (the set of original effici=
ent strategies is</p>
<p style=3D"margin: 0px;">small).</p>
<p style=3D"margin: 0px;">Overall, i believe it would be a reasonably small=
 addition relatively</p>
<p style=3D"margin: 0px;">to gpsd current size.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">Looking forward to your comments.</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">--</p>
<p style=3D"margin: 0px;">Olivier Cornu</p>
<p style=3D"margin: 0px;">&nbsp;</p>
<p style=3D"margin: 0px;">&nbsp;</p></body></html>
--=_8eadec307a2a9fe89f93b7889a20125c--




From MAILER-DAEMON Thu Jul 12 11:43:30 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SpLYA-0006Lr-6i
	for mharc-gpsd-dev@gnu.org; Thu, 12 Jul 2012 11:43:30 -0400
Received: from eggs.gnu.org ([208.118.235.92]:45312)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpLY4-0006Jx-TM
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 11:43:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpLXz-0002fx-1B
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 11:43:24 -0400
Received: from mail-gg0-f173.google.com ([209.85.161.173]:61313)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpLXy-0002ev-Qn
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 11:43:18 -0400
Received: by ggnp1 with SMTP id p1so2779393ggn.4
	for <gpsd-dev@nongnu.org>; Thu, 12 Jul 2012 08:43:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=WyzPjjEPtThWNPUZy9a1s09Ualz70zlSj62uZrQIhZQ=;
	b=U74g14MQFO+APUFOE9GxXSauNY4aKoIOnac4VI9rVYWJ0W/gfpPZpJzuql2IQPbRKj
	Qj7GPvd0SLwTx4btJXdpTWCqcIn/eOFiapWx6usnqI0uhp4yDDIPQyDT4SUVltyiWhgD
	5gIt/4eqGd8vG0BdHz2+f5aqHxaqhtAAj0WNzrbAfnj+GdBBam7Aj4M3GTq1CJe7TrYm
	UDnbhKWZcPZQVsQvmzxqZxrvy7t2EVTK5JWR+PYV6wu79OZv0RNpsVXDh3y0p0AXs7o8
	JQ7QdAwLFEb1BWXh8a9dwagPZA6w8M7kXJJ2O3CCz9iYgJPDjMETyGCQq8hYv4YWAu47
	iCyw==
Received: by 10.101.23.4 with SMTP id a4mr18217761anj.13.1342107798174; Thu,
	12 Jul 2012 08:43:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Thu, 12 Jul 2012 08:42:58 -0700 (PDT)
In-Reply-To: <1SpKUA-0MjYhM0@fwd23.aul.t-online.de>
References: <CAFLV7-ztEePCh1RRd7hwApY+9kKoonOupMWjJt_Chu-it8q39w@mail.gmail.com>
	<1SpKUA-0MjYhM0@fwd23.aul.t-online.de>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Thu, 12 Jul 2012 17:42:58 +0200
Message-ID: <CAFLV7-zrVmBN=CgbGmmS4BE8CCxyPTbcARDKnWhNLwy+4BodcQ@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: multipart/alternative; boundary=00504502eb958f7d1804c4a3d279
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.161.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Virtual devices (as a solution to multiple sources
	location)
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 15:43:28 -0000

--00504502eb958f7d1804c4a3d279
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jul 12, 2012 at 4:35 PM, Reinhard.Arlt@t-online.de <
Reinhard.Arlt@t-online.de> wrote:

> If you connect only the position sources to the first gpsd, and all other
> sensors to the second, all should be fine,
>
> but for a nmea2000 system, i can not do this, so here all unneeded
> messages from other sensors has be forwarded by the
>
> intermediate daemon.
>

I'm not sure i understand the impact of NMEA2000 on this discussion. Is it
because of its multiple-talker, multiple-listener design?
Could you elaborate?


Regards,
--
Olivier

--00504502eb958f7d1804c4a3d279
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Thu, Jul 12, 2012 at 4:35 PM, <a href=3D"mail=
to:Reinhard.Arlt@t-online.de">Reinhard.Arlt@t-online.de</a> <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Reinhard.Arlt@t-online.de" target=3D"_blank">Reinh=
ard.Arlt@t-online.de</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><p style=3D"margin:0px">If you connect only =
the position sources to the first gpsd, and all other sensors to the second=
, all should be fine,</p>


<p style=3D"margin:0px">but for a nmea2000 system, i can not do this, so he=
re all unneeded messages from other sensors has be forwarded by the</p>
<p style=3D"margin:0px">intermediate daemon.</p></blockquote><div><br></div=
><div>I&#39;m not sure i understand the impact of NMEA2000 on this discussi=
on. Is it because of its=A0<span style=3D"background-color:rgb(255,255,255)=
;font-family:sans-serif;font-size:13px;line-height:20px">multiple-talker, m=
ultiple-listener</span><span style=3D"background-color:rgb(255,255,255);fon=
t-family:sans-serif;font-size:13px;line-height:20px">=A0design?</span></div=
>

<div><span style=3D"background-color:rgb(255,255,255);font-family:sans-seri=
f;font-size:13px;line-height:20px">Could you elaborate?</span></div><div><s=
pan style=3D"background-color:rgb(255,255,255);font-family:sans-serif;font-=
size:13px;line-height:20px"><br>

</span></div><div><span style=3D"background-color:rgb(255,255,255);font-fam=
ily:sans-serif;font-size:13px;line-height:20px"><br></span></div><div><span=
 style=3D"background-color:rgb(255,255,255);font-family:sans-serif;font-siz=
e:13px;line-height:20px">Regards,</span></div>

<div><font face=3D"sans-serif"><span style=3D"line-height:20px">--<br>Olivi=
er<br><br></span></font></div></div>

--00504502eb958f7d1804c4a3d279--


From MAILER-DAEMON Thu Jul 12 13:44:39 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SpNRP-0003Mi-AM
	for mharc-gpsd-dev@gnu.org; Thu, 12 Jul 2012 13:44:39 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39308)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpNRH-0003M5-S9
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 13:44:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpNRH-0005fS-0o
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 13:44:31 -0400
Received: from mailout10.t-online.de ([194.25.134.21]:57638)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SpNRG-0005fL-NR
	for gpsd-dev@nongnu.org; Thu, 12 Jul 2012 13:44:30 -0400
Received: from fwd19.aul.t-online.de (fwd19.aul.t-online.de )
	by mailout10.t-online.de with smtp 
	id 1SpNRF-0007hb-Af; Thu, 12 Jul 2012 19:44:29 +0200
Received: from localhost
	(GuZw4gZZZh4zI1-b3RbpEFKo3E-rr+h8okFhPydpTD1cTsk8oB4BL+bnyV-wycLQ5m@[172.20.101.250])
	by fwd19.aul.t-online.de
	with esmtp id 1SpNR8-1zgyye0; Thu, 12 Jul 2012 19:44:22 +0200
MIME-Version: 1.0
Received: from 89.183.38.14:58316 by cmpweb20.aul.t-online.de with HTTP/1.1
	(NGCS V4-0-6-1 on API V3-11-12-2)
Date: Thu, 12 Jul 2012 19:44:22 +0200
To: "gpsd-dev" <gpsd-dev@nongnu.org>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-1
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Message-ID: <1SpNR8-1zgyye0@fwd19.aul.t-online.de>
X-ID: GuZw4gZZZh4zI1-b3RbpEFKo3E-rr+h8okFhPydpTD1cTsk8oB4BL+bnyV-wycLQ5m@t-dialin.net
X-TOI-MSGID: bd701664-2b3c-4bf4-ae9f-810c06928023
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.21
Subject: [gpsd-dev] =?utf-8?q?Fw=3A_Re=3A__Virtual_devices_=28as_a_solutio?=
 =?utf-8?q?n_to_multiple_sources_location=29?=
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 17:44:37 -0000

Hello, 

i have implemented each physical device on the nmea2000 bus as a
device in gpsd. 

For a user, it look like each device is connected by it's own serial
link. 

So a gpsd listen to the position sources, but also to other sources
like wind speed and direction, 

the sounder, the log, ais and so on. 

The intermediate daemon has to collect the data from the position
sources, 

merge them into one position, and forward them to the second gpsd. 

In a system with separate links, i would connect all the other (non
position) sensors to the second gpsd. 

In my opinion, the intermediate daemon should simply forward all non
position data. 

The intermediate deamon could also feed the position data back to its
own daemon, 

if we all agree to introduce something like a default device, 

may be set by a command to the control port, that all clients use, 

that do no wish to connect to a special device. 

Reinhard  

-----Original-Nachricht----- 

Von: Olivier Cornu <o.cornu@gmail.com> 

An: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de> 

Cc: gpsd-dev@nongnu.org 

Betreff: Re: [gpsd-dev] Virtual devices (as a solution to multiple
sources location) 

Datum: Thu, 12 Jul 2012 17:42:58 +0200 

On Thu, Jul 12, 2012 at 4:35 PM, Reinhard.Arlt@t-online.de [1] 

<Reinhard.Arlt@t-online.de [2]> wrote: 

If you connect only the position sources to the first gpsd, and all 

other sensors to the second, all should be fine, 

but for a nmea2000 system, i can not do this, so here all unneeded 

messages from other sensors has be forwarded by the 

intermediate daemon. 

I&#39;m not sure i understand the impact of NMEA2000 on this 

discussion. Is it because of its multiple-talker, 

multiple-listener design? Could you elaborate? 

Regards, -- 

Olivier 





From MAILER-DAEMON Fri Jul 13 09:36:33 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Spg2r-0008En-8p
	for mharc-gpsd-dev@gnu.org; Fri, 13 Jul 2012 09:36:33 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39438)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Spg2l-0008Cd-7e
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 09:36:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Spg2e-0000Nf-FR
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 09:36:27 -0400
Received: from mail-yw0-f45.google.com ([209.85.213.45]:65003)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Spg2e-0000NZ-B8
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 09:36:20 -0400
Received: by yhpp34 with SMTP id p34so1835974yhp.4
	for <gpsd-dev@nongnu.org>; Fri, 13 Jul 2012 06:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	bh=nZeC9je/fFU9u3aTujJNYBQovXH/nynqVtgV2CFYLrI=;
	b=d2ZtJ/FW9ZsXt0GDjdDXoHyFAOY+bT5eXqrY0s2tldyfI1+ClMCHmWPvYrfCYvKzzR
	46C3T+KnU3bci3mlGYpZQSbR9oOCUZ9D8CtZp9hmdP3tsZFJF7XDZqI3K7JkmeZI0rk1
	Ppq71tc9zo3jVzw2yV57jK1kvMwR59cWy3D21OVtVGlQKzgI4g7Z6dIOQemksFzcuGU+
	OYTXjPEfeoOfDhm1v0r2dQBA+jWLb16qrguiM+7Qwwf6FQ67BlHy5X5Ni4fgjXJLhVi3
	A8+CF+c02krbdQo0MikAlFkEG2gkpWe4N60c7eiSBxnR6sYidodt8YFTsZY8f9+6Mt+r
	fHpQ==
Received: by 10.236.183.198 with SMTP id q46mr1041897yhm.107.1342186579719;
	Fri, 13 Jul 2012 06:36:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Fri, 13 Jul 2012 06:35:59 -0700 (PDT)
In-Reply-To: <1SpNR8-1zgyye0@fwd19.aul.t-online.de>
References: <1SpNR8-1zgyye0@fwd19.aul.t-online.de>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Fri, 13 Jul 2012 15:35:59 +0200
Message-ID: <CAFLV7-xNxTT84MdC9Fg1bsCa80UMWC4NQr+oMOOm9qcGmh-kuA@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.45
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Fw: Re: Virtual devices (as a solution to multiple
 sources location)
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 13:36:31 -0000

On Thu, Jul 12, 2012 at 7:42 PM, Reinhard.Arlt@t-online.de
<Reinhard.Arlt@t-online.de> wrote:
> The intermediate daemon has to collect the data from the position sources=
,
> merge them into one position, and forward them to the second gpsd.
>
> In a system with separate links, i would connect all the other (non posit=
ion) sensors to the second gpsd.
> In my opinion, the intermediate daemon should simply forward all non posi=
tion data.

I think i get it now. You would do this:

    Location sensors                    Other sensors
         =E2=86=93=E2=86=93=E2=86=93=E2=86=93                              =
 =E2=86=93=E2=86=93=E2=86=93=E2=86=93
         Gpsd(1) =E2=86=92 Locations_mixer_daemon =E2=86=92 Gpsd(2) =E2=86=
=92 Client_app

But as NMEA2000 setups usually have a single physical link, what you
end up with is:

    All NMEA2000 sensors
            =E2=86=93
          Gpsd =E2=86=92 Location_mixer_daemon =E2=86=92 Client_app

=E2=80=A6 which supposes the mixer daemon proxies non-location events. Is t=
hat it?

If the mixer layer is a daemon, it will proxy all location events too:
we just need to *add* streams (like best guess location), not remove
any.
In fact, it's mainly going to be a proxy for gpsd events:
 1. It will run on port 2947 and use a slave gpsd instance on another
port, as Eric suggested
 2. It will speak the gpsd protocol, because that's what client speak
and expect from port 2947
 3. It will have to proxy all original gpsd events (TPV, SKY=E2=80=A6) beca=
use
clients of port 2947 may very well require them
 4. It will also have to proxy some client requests targeted at the
gpsd instance (?WATCH, etc)
 6. Most likely, its only source will ever be gpsd: event sources
should be integrated at the multiplexer level anyway

But it will also have to duplicate lots of gpsd features:
 7. It will have to count clients and connect to the slave gpsd only
if at least one client is connected (in fact, the similar gpsd code
probably becomes irrelevant, as a gpsd process could be summoned when
needed and killed when not in use)
 8. It will have to duplicate the subscribers/dispatching code in
order to broadcast the relevant stuff to the right listener, as it
would become the /de facto/ "outgoing multiplexer" (only one client
connection to the "incoming multiplexer" slave gpsd instance), making
similar gpsd code useless

And most likely more=E2=80=A6
Overall, it will burn a lot of resources just pretending it is gpsd.
In fact, *most* of its runtime resources will be spent in
gpsd-duplicated code, pretending it's gpsd. It's a high price to pay
for (supposedly) a UNIX inspired architecture purity, with few
practical cases -- if any -- to legitimate the cost.
So, to save on these new costs, it would probably end up linking
dynamically with the slave gpsd code (instead of using a socket).

What this tells me is that perhaps multiplexing and mixing are too
close to be stretched in two daemons. It's like putting a firewall and
a switch/router in the same box: it makes sense. If gpsd handles both,
it becomes possible to pile gpsd intances up like Lego blocks.
For example, your initial scheme would become:

    Location sensors   Other sensors
          =E2=86=93=E2=86=93=E2=86=93=E2=86=93            =E2=86=93=E2=86=
=93=E2=86=93=E2=86=93
          Gpsd(1)    =E2=86=92    Gpsd(2)   =E2=86=92   Client_app

This is the kind of architectural quality i like. :-)


Regards,

--
Olivier Cornu


From MAILER-DAEMON Fri Jul 13 10:16:20 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SpgfM-0001RI-8o
	for mharc-gpsd-dev@gnu.org; Fri, 13 Jul 2012 10:16:20 -0400
Received: from eggs.gnu.org ([208.118.235.92]:36504)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SpgfE-0001R6-RC
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 10:16:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Spgf9-00063z-3y
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 10:16:12 -0400
Received: from mail-gh0-f173.google.com ([209.85.160.173]:54319)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Spgf8-00063v-Uu
	for gpsd-dev@nongnu.org; Fri, 13 Jul 2012 10:16:07 -0400
Received: by ghrr14 with SMTP id r14so3951396ghr.4
	for <gpsd-dev@nongnu.org>; Fri, 13 Jul 2012 07:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	bh=fAm755pVmvQcZr09v7HvqQ6O/2UoImOuPAZZvIrw+L4=;
	b=bMBSqb4sCApw9D38y5s7fsKbkoziNJ0a9kijNNoPZlPzkWxJorqEiwdDYRtJyTe6r9
	9DqoEdDgjlTXViWy1Hi3CgiqeLjBBhRG+pHFEa0ounMhX0InquVCtUnq9a6FMYzD9Wyx
	ByFTuv5JOIk9Ps9/VJsYecmNjfG3hVtvWfpcuwm3iRGyBdF2pxjx15Ltgh8Tk/qY7Mh9
	Zqx6LNZlp7ol8g5ePO+ZY3NsYYFQq/bTLH2WS9itLnIUlIea7A7EwVWzWzczXjfUF/VK
	c4xNRhnHh+m6BYowvvZW4I8qoELlaGYA4pjHr2L38JIUztQLPlH0WKz7c04HRMsClgGM
	l+BA==
Received: by 10.236.185.198 with SMTP id u46mr1272881yhm.33.1342188966566;
	Fri, 13 Jul 2012 07:16:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Fri, 13 Jul 2012 07:15:46 -0700 (PDT)
In-Reply-To: <CAFLV7-xNxTT84MdC9Fg1bsCa80UMWC4NQr+oMOOm9qcGmh-kuA@mail.gmail.com>
References: <1SpNR8-1zgyye0@fwd19.aul.t-online.de>
	<CAFLV7-xNxTT84MdC9Fg1bsCa80UMWC4NQr+oMOOm9qcGmh-kuA@mail.gmail.com>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Fri, 13 Jul 2012 16:15:46 +0200
Message-ID: <CAFLV7-wpA7-6YupM4Mrrbp0hn9N4rLWnbEZDYxVFZJX10rxjOQ@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.173
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Fw: Re: Virtual devices (as a solution to multiple
 sources location)
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 14:16:18 -0000

On Fri, Jul 13, 2012 at 3:35 PM, Olivier Cornu <o.cornu@gmail.com> wrote:
> If the mixer layer is a daemon, it will proxy all location events too:
> we just need to *add* streams (like best guess location), not remove
> any.

I feel i need to emphasize this bit: basically, we only need to add
another (TPV, SKY?) stream. From an architectural point of view,
building a whole daemon for this sole purpose is overkill. We only
need to add one virtual device.
All the duplicate effort required should flash as an architectural warning =
sign=85

--
Olivier Cornu


From MAILER-DAEMON Sat Jul 14 08:21:12 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sq1LU-0006wi-2F
	for mharc-gpsd-dev@gnu.org; Sat, 14 Jul 2012 08:21:12 -0400
Received: from eggs.gnu.org ([208.118.235.92]:58072)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Sq1LR-0006wB-I8
	for gpsd-dev@nongnu.org; Sat, 14 Jul 2012 08:21:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Sq1LP-000488-Ol
	for gpsd-dev@nongnu.org; Sat, 14 Jul 2012 08:21:09 -0400
Received: from mail-gh0-f173.google.com ([209.85.160.173]:63601)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1Sq1LP-000483-J5
	for gpsd-dev@nongnu.org; Sat, 14 Jul 2012 08:21:07 -0400
Received: by ghrr14 with SMTP id r14so4698907ghr.4
	for <gpsd-dev@nongnu.org>; Sat, 14 Jul 2012 05:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=BsnNUcBQsGnxptwsvSQURT+5AbC0qB/EcWz8eOqkoX0=;
	b=afkXYYi3zOiSZk5Fo/2S6XQW0CJ/QpFSCCXEgcXXeHa1U5650ew6dB8qHAf1SqMzF+
	rN7sFLMpnAnPO+AGHFULodHLKlrhIrtMeNzPV9NKVZnX1smU8nOW1noQbHNVkyZx9RC+
	yogizvoNsSqJfq3BHdzIGfGftj5OqpRiBou1BCY62rdTafmHrkInZ4m3tjICH3fwxaXJ
	y8fYB2ixAx7v26cNWlsFTHMWrIM99K4lfc2SSx8VGfZ2qVtEZbHPxJCc0+nNnEe1ZoR8
	LJ2a+QYbiqCHvlCFytelJfIkQPnNsQ6CNRXxs8RDF6ccmRRWNKxK6vwbpQrR749gTmK0
	MGow==
Received: by 10.101.23.4 with SMTP id a4mr1318028anj.13.1342268467063; Sat, 14
	Jul 2012 05:21:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Sat, 14 Jul 2012 05:20:46 -0700 (PDT)
In-Reply-To: <20120710121925.547b13b5.gem@rellim.com>
References: <20120709141709.GA3402@thyrsus.com>
	<1SoW8R-0wTutM0@fwd02.aul.t-online.de>
	<20120710121925.547b13b5.gem@rellim.com>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Sat, 14 Jul 2012 14:20:46 +0200
Message-ID: <CAFLV7-wf_7gKEMTmspDrczk6e24bRhfGKh2UEm7Npe9F9-CTmg@mail.gmail.com>
To: "Gary E. Miller" <gem@rellim.com>
Content-Type: multipart/alternative; boundary=00504502eb952c2d2d04c4c93b51
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.173
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] Using multiple location sources to improve accuracy
 and reliability
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2012 12:21:10 -0000

--00504502eb952c2d2d04c4c93b51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 10, 2012 at 9:19 PM, Gary E. Miller <gem@rellim.com> wrote:

>
> On Tue, 10 Jul 2012 10:49:31 +0200
> "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de> wrote:
> >       For me the point is, that there is already so much code in
>  > gpsd that address the needs of only very few people, and this options
> > need difficult configuration, and it may be implemented in so many
> > different ways.
>
> Yup.
>

There is also much code violating the separation principle: what do wind
direction or sea temperature have to do with GPS devices and gpsd, for
example? I guess such things get included only because they share the same
NMEA protocol than GPS devices (and sometimes the same physical line). If
we were serious about separation, these should go into their own nmead, not
gpsd, right?
How is best-guess fix code any different? It also shares a protocol (gpsd)
and a logical line (GPS=E2=86=92client); And it happens to have something t=
o do
with GPS devices and your actual location.

How come water temperature or AIS rightfully belong to gpsd and a
best-guess fix does not?
I'm not asking for the favor of including alien code because other alien
code got included too. Just saying: get your story straight.
If policy is what makes the difference, in other words if gpsd actually is
a sensor multiplexer, then it should change its name to reflect that
choice: what about sensord? No matter how you put it, it is quite
reasonable to expect a gpsd software to actually provide serious (i.e. best
effort) GPS-based location data.  :-)

Now, if gpsd actually is sensord, i do agree a locationd daemon can make
sense. Yet it would still be a virtual device getting all its input from
sensord and broadcasting its messages to clients through sensord as well.
So i'd keep arguing it's architecturally sound and computationally more
efficient to implement such necessary virtual devices (no matter their
implementation is policy-based or only "mechanical" or anything else) into
sensord rather than in distinct daemons. In fact, i'd also argue that
segregating among virtual devices based on what they do with the available
data is probably an architectural mistake: as long as they comply with the
virtual device interface, it's none of our multiplexer business.

--
Olivier Cornu

--00504502eb952c2d2d04c4c93b51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Jul 10, 2012 at 9:19 PM, Gary E. Miller =
<span dir=3D"ltr">&lt;<a href=3D"mailto:gem@rellim.com" target=3D"_blank">g=
em@rellim.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><br>
On Tue, 10 Jul 2012 10:49:31 +0200<br>
&quot;<a href=3D"mailto:Reinhard.Arlt@t-online.de">Reinhard.Arlt@t-online.d=
e</a>&quot; &lt;<a href=3D"mailto:Reinhard.Arlt@t-online.de">Reinhard.Arlt@=
t-online.de</a>&gt; wrote:<br>&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0For me the poi=
nt is, that there is already so much code in</div>

<div class=3D"im">
&gt; gpsd that address the needs of only very few people, and this options<=
br>
&gt; need difficult configuration, and it may be implemented in so many<br>
&gt; different ways.<br>
<br>
</div>Yup.<br></blockquote><div><br></div><div>There is also much code viol=
ating the separation principle: what do wind direction or=C2=A0sea temperat=
ure have=C2=A0to do with GPS devices and gpsd, for example?=C2=A0I guess su=
ch things get included only because they share the same NMEA protocol than =
GPS devices (and sometimes the same physical line). If we were serious abou=
t separation, these should go into their own nmead, not gpsd, right?</div>

<div>How is best-guess fix code any different? It also shares a protocol (g=
psd) and a logical line (GPS=E2=86=92client); And it happens to have someth=
ing to do with GPS devices and your actual location.</div><div><br></div><d=
iv>
How come water temperature or AIS rightfully belong to gpsd and a best-gues=
s fix does not?</div>
<div>I&#39;m not asking for the favor of including alien code because other=
 alien code got included too. Just saying: get your story straight.</div><d=
iv>If policy is what makes the difference, in other words if gpsd actually =
is a sensor multiplexer, then it should change its name to reflect that cho=
ice: what about sensord?=C2=A0No matter how you put it, it is quite reasona=
ble to expect a gpsd software to actually provide serious (i.e. best effort=
) GPS-based location data. =C2=A0:-)</div>

<div><br></div><div>Now, if gpsd actually is sensord, i do agree a location=
d daemon can make sense. Yet it would still be a virtual device getting all=
 its input from sensord and broadcasting its messages to clients through se=
nsord as well.</div>

<div>So i&#39;d keep arguing it&#39;s architecturally sound and=C2=A0comput=
ationally=C2=A0more efficient to implement such necessary virtual devices (=
no matter their implementation is policy-based or only &quot;mechanical&quo=
t; or anything else) into sensord rather than in distinct daemons. In fact,=
 i&#39;d also argue that segregating among virtual devices based on what th=
ey do with the available data is probably an architectural mistake: as long=
 as they comply with the virtual device interface, it&#39;s none of our mul=
tiplexer business.</div>

<div><br></div><div>--</div><div>Olivier Cornu<br><br></div></div>

--00504502eb952c2d2d04c4c93b51--


From MAILER-DAEMON Tue Jul 17 11:54:12 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SrA6F-0000j9-Vc
	for mharc-gpsd-dev@gnu.org; Tue, 17 Jul 2012 11:54:12 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60921)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SrA6C-0000Y2-8f
	for gpsd-dev@nongnu.org; Tue, 17 Jul 2012 11:54:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SrA67-0003OJ-BH
	for gpsd-dev@nongnu.org; Tue, 17 Jul 2012 11:54:08 -0400
Received: from mail-yw0-f45.google.com ([209.85.213.45]:64243)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SrA67-0003Ni-6g
	for gpsd-dev@nongnu.org; Tue, 17 Jul 2012 11:54:03 -0400
Received: by yhpp34 with SMTP id p34so550112yhp.4
	for <gpsd-dev@nongnu.org>; Tue, 17 Jul 2012 08:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type
	:content-transfer-encoding;
	bh=794ZpoE4RThqyoA30Dmtl6X+8GX+0KQA0U4H0CL+QDU=;
	b=tL1mNY4j8phkoNZ5fBMeSs7cjxMw+qnsrlgIMSkMV6ut+ZxauHZYrMhDWoQICroCOf
	S2MVkjf2ZMp/sOJBobcB1QjWmz+CvjANfV7KEtA1+i2RHUFmxtSlAuXM5K6a0drm/WFX
	WbYtd3E10q0E9+k/JKbrjxsb/aPViPDX/8hkjEYTFSIsPtzaz6MKHt79O3pVBgRcueht
	cvV7Y9hFSPUcC9/upbo6Z8eVWVi6OmE1R+dpoT2pqqFrw1BfEm9YGoPPvZU3Nyksx6Gp
	8zv5dX6wYxj9q4Qj1xYZ/892ECv91aE/IlrN/0QAsauRFiXi9IaR7OOVL+NUt1OwZZtX
	Jk9Q==
Received: by 10.236.9.102 with SMTP id 66mr2302847yhs.55.1342540441728; Tue,
	17 Jul 2012 08:54:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Tue, 17 Jul 2012 08:53:41 -0700 (PDT)
From: Olivier Cornu <o.cornu@gmail.com>
Date: Tue, 17 Jul 2012 17:53:41 +0200
Message-ID: <CAFLV7-xbznOAQAWn=QGF6hDTU1jJG_682PAa3AMH_0mngUJtvg@mail.gmail.com>
To: gpsd-dev <gpsd-dev@nongnu.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.45
Subject: [gpsd-dev] Virtual sensors and gpsd architectures
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 15:54:10 -0000

Playing around gpsd's architecture and the design challenge of
elegantly introducing virtual sensors somewhere in the loop between
real sensors and final clients, i came up with a few graphs (hopefully
worth N words).
So i engaged in summarizing the different alternatives, using these
graphs as illustration.

In the following, I take for granted that the proper abstraction to
solve this whole problem is the _virtual_sensor_ (VS): it's a simple
"mechanical" concept, thus with a clean interface, neutral and
abstract enough to allow for pretty much anything.
Most of what comes would still apply to a different concept though, in
case you can't stand the VS paradigm.


VIRTUAL SENSORS

A virtual sensor can do any kind of computation based on other sensors
data and provide the result in a sensor format.
For example, it may import data from a web service such as
http://marinetraffic.com/ and publish a corresponding stream of gpsd
AIS messages. It appears to clients as another JSON DEVICE, that can
be activated, POLLed, WATCHed, etc.
Most often, it works with local sensor(s) data to provide an altered
(or compound) stream, enforcing one particular policy: stricter fix
requirements, best-effort location, sensor divergence alarm=E2=80=A6 It
subscribes to other DEVICE streams like any gpsd client.

In a typical setup, several virtual sensors are available: client apps
get to choose which sensor (virtual or not) they listen to, because
different clients may have different needs.
They simply connect to gpsd, query the available DEVICE list and pick
their favorite(s) sensor(s).
When a VS is WATCHed, it gets activated (unless it already was). Upon
activation, it activates and WATCHes local "slave" sensors, if any; It
releases them when it gets inactivated.


GPSD ARCHITECTURE

The previous threads have made it clear gpsd is a =C2=ABmechanical
multiplexer=C2=BB: it gathers data from sensors and broadcast them to
clients.
In a classic multi-producer/multi-consumer scenario, its sensor data
flow basically looks like this:

        S1  S2  S3        Sensors
          =E2=86=98 =E2=86=93 =E2=86=99
           gpsd           Multiplexer
          =E2=86=99 =E2=86=93 =E2=86=98
        C1  C2  C3        Clients

Technically speaking though, gpsd is both a multiplexer (gathering
input signal) and a demultiplexer (broadcasting output signal):

        S1  S2  S3        Sensors
          =E2=86=98 =E2=86=93 =E2=86=99
     =E2=95=AD-    mux            Multiplexer
gpsd |      =E2=87=93
     =E2=95=B0-   demux           Demultiplexer
          =E2=86=99 =E2=86=93 =E2=86=98
        C1  C2  C3        Clients

The distinction is important to make when talking about virtual
sensors, because they both:
 - receive sensors data
 - provide data to clients
Thus, computationally speaking, they optimally come after mux and before de=
mux:

       S1  S2  S3        Sensors
         =E2=86=98 =E2=86=93 =E2=86=99
          mux            Multiplexer
           =E2=87=93
           VS            Virtual Sensor
           =E2=87=93
         demux           Demultiplexer
         =E2=86=99 =E2=86=93 =E2=86=98
       C1  C2  C3        Clients


INTERNAL VIRTUAL SENSORS

In such a scenario, virtual sensors follow the optimal computational
logic and insert themselves into gpsd, between the mux and demux
layers.
A VS manager may handle multiple VS and run then on demand. The sensor
data flow is the following:

          mux            Multiplexer
           =E2=87=93
   VS1 =E2=87=86  vsm  =E2=87=84 VS2    Virtual Sensors, VS Mixer
           =E2=87=93
         demux           Demultiplexer

Note that, in such a design, physical sensor data and related VS data
can be broadcast at the same time.
Virtual sensors can even be chained (use data from another VS) without
introducing noticeable lag either.


EXTERNAL VIRTUAL SENSORS

In this scenario, virtual sensors are pushed back into another
process, plugging itself twice to gpsd: as a sensor and as a client.

        S1  S2  VS_out    Sensors
          =E2=86=98 =E2=86=93 =E2=86=99   =E2=87=91
           gpsd    =E2=95=91      Mux/Demux
          =E2=86=99 =E2=86=93 =E2=86=98   =E2=95=91
        C1  C2  VS_in     Clients

Note that, in such a design, virtual sensors lag compared to their
source sensors: transport costs aside, data must got through an
additional gpsd mux-demux cycle.
Consecutively, the lag gets worse if VS are chained: each new VS layer
adding its own cycle, unless there is a single VS manager process
hosting all chained VS.


VIRTUAL SENSOR PROXY

An alternative external design has been proposed by esr: the VS runs
on top of gpsd, as =C2=AB a proxy daemon that launches GPSD reporting to a
private port, reads the JSON from that, does whatever (...) you want,
and ships results to port 2947 as if it were GPSD =C2=BB.

        S1  S2  S3        Sensors
          =E2=86=98 =E2=86=93 =E2=86=99
           gpsd           Mux/Demux
            =E2=86=93
           vsd            VS Mixer and (Mux/)Demux
          =E2=86=99 =E2=86=93 =E2=86=98
        C1  C2  C3        Clients

Note that, in such a design, there is no lag between physical sensor
data and VS data: they both suffer the same additional mux-demux cycle
lag introduced by vsd.
The vsd daemon indeed needs to duplicate gpsd features, such as a
demux to serve clients on demand -- and a mux if data were to come
from several gpsd instances. In fact, such daemon would basically be
an internal VS/gpsd design, stripped of its physical sensor logic.


COMPARATIVE MERITS

Internal VS run fastest, consume less resources and introduce no lag.
Some VS drivers can be shipped with gpsd: they are important enough
and require the same overall quality other gpsd code requires.
But an internal VS manager also touches gpsd core code, so it's also
the most pervasive alternative. If sensor and client interfaces are
well defined, it should be a rather light touch though (in fact, VS
implementation provides a good check they are).

On the other hand, external VS are the least intrusive: they can live
without requiring any change in core code, at least ideally. They
still require gpsd quality though and should rather remain in the
project's control (at least the VS manager bit).
External VS run slower, consume more resources and introduce lag. But
they can provide a remote mechanism for client apps to publish the
additional/custom VS they'd need.

The proxy design is not well suited to the virtual sensor paradigm: it
is doomed to duplicate lots of gpsd code and impersonate the port 2947
service, which is dangerous. With its slave gpsd instance, it would be
better suited to a gspd controller paradigm.


CONCLUSION

Eventually, it would be best to offer both options as they address
different scenarios.
Yet, in the end, my guess is that:
 - most users would rather see such code shipped with a gpsd seal, and
run optimally
 - most client apps would rather focus on their part and leave that
code to gpsd as well
 - consecutively, internal use would far exceed external use

Unsurprisingly, project maintainers would rather start external to
test the logic, and maybe integrate it later when it's mature enough;
An individual contributor like myself would rather start internal to
test the logic rapidly, and maybe export it to a remote process when
it's mature enough.
A git branch would allow us to take the fast path and multiply tests
without prematurely impacting everyone. Added benefit: it would be
guaranteed to get merged without unnecessary delays, because esr hates
to see code rotting there=E2=80=A6 ;-)


--
Olivier Cornu


From MAILER-DAEMON Sat Jul 21 11:45:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Ssbrq-0001Do-76
	for mharc-gpsd-dev@gnu.org; Sat, 21 Jul 2012 11:45:18 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60494)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ukyg9e5r6k7gubiekd6@yahoo.com>) id 1SrrFq-0004jt-TR
	for gpsd-dev@nongnu.org; Thu, 19 Jul 2012 09:59:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ukyg9e5r6k7gubiekd6@yahoo.com>) id 1SrrFm-000567-Rb
	for gpsd-dev@nongnu.org; Thu, 19 Jul 2012 09:58:58 -0400
Received: from nm1.bullet.mail.bf1.yahoo.com ([98.139.212.160]:44309)
	by eggs.gnu.org with smtp (Exim 4.71)
	(envelope-from <ukyg9e5r6k7gubiekd6@yahoo.com>) id 1SrrFm-00055u-Lu
	for gpsd-dev@nongnu.org; Thu, 19 Jul 2012 09:58:54 -0400
Received: from [98.139.214.32] by nm1.bullet.mail.bf1.yahoo.com with NNFMP;
	19 Jul 2012 13:58:53 -0000
Received: from [98.139.212.213] by tm15.bullet.mail.bf1.yahoo.com with NNFMP;
	19 Jul 2012 13:58:53 -0000
Received: from [127.0.0.1] by omp1022.mail.bf1.yahoo.com with NNFMP;
	19 Jul 2012 13:58:53 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 833548.77951.bm@omp1022.mail.bf1.yahoo.com
Received: (qmail 53627 invoked by uid 60001); 19 Jul 2012 13:58:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1342706333; bh=Ej5tlItczldl5rf9sKJqpTghhTvINhqi0lCfOK+mIN8=;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=biLHxbKmMYC6W4+xWfgdR8kLc8KXK9c0yXV9sJuZdu5s7U00oF2wTeWpeX8sdYa16gSz3INj3kCxygQ76D+hwpE6OYDJqiS5EmskXOB/S2bTOP0gSdw/y+BzFAYiUr3oXq3slY3D4LnedAhz9blNQPveUP9Fi3QXB1us2/CpIbM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=JFwi/LtDBauYpkmTDqupDpbDN42F/2dlcU12Z8O+Z8m5QXH+NqtmO6L8T9GTnQY0lEhVFGuqRUmK1L2zgG3EYWkoJWaVrMqAyi1yaV3gIBh35XB8gjbrRMuGXaJauDw8QrGeN2Y58QvNiWhZYEMIp+3vAkmL59EYU6xhs1esSfU=;
X-YMail-OSG: 1drOTC8VM1nUhRafpqp.Qr40QdoH7I1v4pMUuX46gwxS5DY
	mjLnroTPIPCbiZk_01XYtGZRPHznwYH_SDL4ExEr5MKehTHCliooGcKFX4VQ
	hYLo9m5dcKycC00ViWd1cU495hHVgjOh3iUkH5hrr.nt4OVfwIZDoxeV2919
	tGiBnrsV7b0juCjlqGosowVzA6_BKAW1OjAEGsA6poVfIJvSy.1_L8satj.m
	_pGydz3fT.wlF.fkmCRtuM28eadwXkr7FTnbMm83G3TIrqioRILcApMXDX51
	sz9FXO0x1tdRqWyskSZM4xr7tmuaT7Vejfz9HwRvC2Mt6gF56P_iLKskyTur
	MY_KP7aLfT0uEwQZfp.mhJXi6_4455PcuUyM4CQ_zULBeBJnBWuYlL1kiqMa
	1kQMnxBJ8IiPmanPRTpqApOuCF1Ynfi7D18Yic_DBs9zvzlqh8I7pSYFhzi7
	EDJno5I4DfyxTmQ.jjjF7n.2h3wFJIMjaScDExJinz34EIbTkihIggvDeI3j
	FQ7DuEtMAlfwcQnv0JxLesh5uiMA-
Received: from [124.168.176.110] by web142605.mail.bf1.yahoo.com via HTTP;
	Thu, 19 Jul 2012 06:58:53 PDT
X-Mailer: YahooMailWebService/0.8.120.356233
Message-ID: <1342706333.53559.YahooMailNeo@web142605.mail.bf1.yahoo.com>
Date: Thu, 19 Jul 2012 06:58:53 -0700 (PDT)
From: Ukygerkgubiekd Ukygerkgubiekd <ukyg9e5r6k7gubiekd6@yahoo.com>
To: "gpsd-dev@nongnu.org" <gpsd-dev@nongnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 98.139.212.160
X-Mailman-Approved-At: Sat, 21 Jul 2012 11:45:16 -0400
Subject: [gpsd-dev] Mingw port
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Ukygerkgubiekd Ukygerkgubiekd <ukyg9e5r6k7gubiekd6@yahoo.com>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 13:59:04 -0000

Hi, and thanks for GPSd!=0AMy name's Matt.=0A=0AI'm wanting to raise the to=
pic of a Mingw/Windows port once again, and show some code so you can see t=
he challenges ahead.=0ASo here is an experimental, very hackish port to Min=
gw (native GCC on Windows):=0A=0A=0Agit://github.com/ukyg9e5r6k7gubiekd6/gp=
sd.git=0A=0AUnder Debian x64, the mingw branch compiles without warnings an=
d passes all regression tests.=0AUntil recently it was splint clean, but re=
cently splint began choking with an internal error on libgpsd :-(=0A=0A=0AU=
nder Windows XP, a minimal configuration compiles cleanly, but I have done =
almost no testing.=0Acgps.exe can generate network traffic (TCP SYN dport 2=
479), and some of the test*.exe binaries seem to work.=0A=0AI'm not really =
intending for folks to pull this, though you may like to cherry-pick some o=
f the SConstruct changes.=0AThere's a lot of stuff that's stubbed out, or c=
ompletely untested.=0A=0A=0Aas the code notes, SOCKET is different to fd on=
 Windows (which is again different to Win32 HANDLE).=0A =0AOn this particul=
ar point, it's fairly easy to use the existing socket_t typedef to handle t=
his difference.=0AThis level of abstraction is sufficient to get a TCP-only=
 libgps and its dependents.=0ASome of this has ugly Win32 API calls, where =
Windows lacked POSIX or *NIX functionality, mostly for libgpsd.=0A=0AI thin=
k we have to accept that if we want to get a fully-functional daemon and cl=
ients on Windows.=0ASo abstraction and modularisation is going to be necess=
ary to hide the ugliness and keep things clean.=0A=0AFor example, =0A=0AHow=
ever, Windows has a completely different set of APIs for serial comms, and =
for timing/handshaking/waiting etc.=0A=0ATo get drivers, the daemon and the=
 regression tests working under Windows hence requires some abstraction lay=
er over those differences.=0A=0AMy idea is that such a layer could also inc=
orporate the existing differences between shm, dbus, QT, sockets and fds.=
=0AYour comments appreciated!=0A=0AMatt


From MAILER-DAEMON Sat Jul 21 11:45:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Ssbrq-0001Ec-E8
	for mharc-gpsd-dev@gnu.org; Sat, 21 Jul 2012 11:45:18 -0400
Received: from eggs.gnu.org ([208.118.235.92]:44282)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1SsW6u-0004TC-B1
	for gpsd-dev@nongnu.org; Sat, 21 Jul 2012 05:36:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1SsW6t-0004YJ-6u
	for gpsd-dev@nongnu.org; Sat, 21 Jul 2012 05:36:28 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:42092)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1SsW6t-0004YF-0m
	for gpsd-dev@nongnu.org; Sat, 21 Jul 2012 05:36:27 -0400
Received: by pbbro12 with SMTP id ro12so7568121pbb.4
	for <gpsd-dev@nongnu.org>; Sat, 21 Jul 2012 02:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=msvWfnkr4WzEiSLzWyq+9FLDnUFpMntKvpnOgbGtGW0=;
	b=kY2GVV5MpXIdT00ihFgleHhvZ8KR6fZW/eOKRWC2LDO01DY2rokEdejjSSxeXHh1Xs
	QhoMDF3W2x44qyx/i+fbK2AoE8yeKrP/wLLLXHC8T4m9C7sT1CJrJua40jweRbIQbauf
	S9lz1luMMPH/XU1IR4oNKqYBat41IEALhsfqmT4W8V3KrGemJ/5uIc46gFAPIVfjy7k7
	wUf4ciHR+C/3+EE+yzWwZz29204KuGAcRx9scAvbUnSUwqSrzyjIH0HPlgOcydI+VuUo
	dDxqVnyKiZ58ofyQ9AkFmLy3I1jXX5ag5iEb7nA9zNfasDguMtqpCJ7inU+mG/uheU4E
	Jncw==
MIME-Version: 1.0
Received: by 10.68.217.40 with SMTP id ov8mr18708543pbc.131.1342863385547;
	Sat, 21 Jul 2012 02:36:25 -0700 (PDT)
Received: by 10.68.60.227 with HTTP; Sat, 21 Jul 2012 02:36:25 -0700 (PDT)
Date: Sat, 21 Jul 2012 10:36:25 +0100
Message-ID: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
From: Simon Dawson <spdawson@gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.45
X-Mailman-Approved-At: Sat, 21 Jul 2012 11:45:16 -0400
Subject: [gpsd-dev] ARM/uClibc build problem
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 09:36:29 -0000

Using Buildroot, I'm cross compiling gpsd 3.7 for ARM, using uClibc.
The build is falling over with the following error.

  gpsmon.o: In function `monitor_fixframe':
  gpsmon.c:(.text+0x264): undefined reference to `acs_map'
  monitor_nmea.o: In function `nmea_update':
  monitor_nmea.c:(.text+0xbc0): undefined reference to `acs_map'
  collect2: ld returned 1 exit status
  scons: *** [gpsmon] Error 1
  scons: building terminated because of errors.

I'm working around this by adding the following line to the gpsmon.c
and monitor_nmea.c source files.

  unsigned long acs_map[128];

What I'm wondering is whether there might be a way of resolving this
issue in a less ugly way --- preferably, directly in the gpsd build
system. Does anybody have any suggestions?


From MAILER-DAEMON Sun Jul 22 15:17:58 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1St1fC-0006Pa-IX
	for mharc-gpsd-dev@gnu.org; Sun, 22 Jul 2012 15:17:58 -0400
Received: from eggs.gnu.org ([208.118.235.92]:50708)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1St1fA-0006Nt-3J
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 15:17:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1St1f8-0000yr-W6
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 15:17:56 -0400
Received: from mail-yw0-f45.google.com ([209.85.213.45]:48940)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1St1f8-0000yj-Pq
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 15:17:54 -0400
Received: by yhpp34 with SMTP id p34so5044894yhp.4
	for <gpsd-dev@nongnu.org>; Sun, 22 Jul 2012 12:17:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:cc:content-type;
	bh=1Du7zWCfVVrY9eYlVS/Zm5rcuDNdHgItCRIkA17shTM=;
	b=j239kY9IfWQCIAqOQIQSla2w595UaI9579H+DjcOsknVmWbovfNOOIfZNvk+u+qeI9
	hHBEKtRb7JWfS1BL24cplKB2+70ukDsPxQHgu8P2Po+F9N/vy8t5xPR6y7GXJrlpaWUT
	UnZEgpQ35HLmjVtl3mHhWZtmR2ngjLCyrTExwOINEu9gND/SabjNCG6TSagKYQlcN2d/
	9F88cD+4uKzAjeQsETYYM1hiByXDIfXgq+GjJ5LPEFInU8rQ+OMdbv7nZBoeLq1urYNs
	cXOxH1mNd/Ek1jp6L5yrlr5pi3wVZvAi5Jjfr2PgBQwWClC/QUX9NjPtbXbOXwyJ7OF/
	7RVQ==
Received: by 10.236.185.198 with SMTP id u46mr12292610yhm.33.1342984673813;
	Sun, 22 Jul 2012 12:17:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Sun, 22 Jul 2012 12:17:33 -0700 (PDT)
From: Olivier Cornu <o.cornu@gmail.com>
Date: Sun, 22 Jul 2012 21:17:33 +0200
Message-ID: <CAFLV7-wras2OUqd-GOqupbbeC+SXZjo5TeebN_VScALkJKDhLw@mail.gmail.com>
To: gpsd-dev <gpsd-dev@nongnu.org>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.45
Subject: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 19:17:57 -0000

The master branch currently fails the valgrind audit with:

$ scons -c && scons && scons valgrind-audit
(...)
gpsd:WARN: exiting.
==2037==
==2037== HEAP SUMMARY:
==2037==     in use at exit: 272 bytes in 1 blocks
==2037==   total heap usage: 65 allocs, 64 frees, 11,690 bytes allocated
==2037==
==2037== 272 bytes in 1 blocks are possibly lost in loss record 1 of 1
==2037==    at 0x4C29DB4: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2037==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==2037==    by 0x559CABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==2037==    by 0x40810B: ntpd_link_activate (in /home/olivier/dev/gpsd/gpsd)
==2037==    by 0x407396: gpsd_add_device (in /home/olivier/dev/gpsd/gpsd)
==2037==    by 0x403A68: main (in /home/olivier/dev/gpsd/gpsd)
==2037==
==2037==
==2037== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ----
==2037== LEAK SUMMARY:
==2037==    definitely lost: 0 bytes in 0 blocks
==2037==    indirectly lost: 0 bytes in 0 blocks
==2037==      possibly lost: 272 bytes in 1 blocks
==2037==    still reachable: 0 bytes in 0 blocks
==2037==         suppressed: 0 bytes in 0 blocks
==2037==
==2037== For counts of detected and suppressed errors, rerun with: -v
==2037== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
scons: done building targets.

I've bisected the issue back to commit 1ee8e4d601d: Move nowait out of
gpsd_add_device.
I haven't investigated any further.

Most likely, this has gone unnoticed thanks to bug #36919 [1]: "scons
valgrind-audit" does not audit local freshly-built gpsd instance.


Regards,

--
Olivier Cornu

[1] https://savannah.nongnu.org/bugs/?36919


From MAILER-DAEMON Sun Jul 22 18:40:58 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1St4pe-0007SQ-Kk
	for mharc-gpsd-dev@gnu.org; Sun, 22 Jul 2012 18:40:58 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60642)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1St4pb-0007RB-Ii
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 18:40:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1St4pa-0004EC-EL
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 18:40:55 -0400
Received: from mailout05.t-online.de ([194.25.134.82]:34420)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1St4pZ-0004C4-Us
	for gpsd-dev@nongnu.org; Sun, 22 Jul 2012 18:40:54 -0400
Received: from fwd51.aul.t-online.de (fwd51.aul.t-online.de )
	by mailout05.t-online.de with smtp 
	id 1St4pX-0003sY-DL; Mon, 23 Jul 2012 00:40:51 +0200
Received: from localhost
	(b71bguZDYh1xGiadWDs5jLjn-QGpNALDAIIHBYNRG9ytm8YBVPo5mZ9SF0q1UpiZzX@[172.20.101.250])
	by fwd51.aul.t-online.de
	with esmtp id 1St4pN-07Y1Eu0; Mon, 23 Jul 2012 00:40:41 +0200
MIME-Version: 1.0
Received: from 79.218.118.208:49918 by cmpweb25.aul.t-online.de with
	HTTP/1.1 (NGCS V4-0-6-4 on API V3-11-12-2)
In-Reply-To: <CAFLV7-wras2OUqd-GOqupbbeC+SXZjo5TeebN_VScALkJKDhLw@mail.gmail.com>
References: <CAFLV7-wras2OUqd-GOqupbbeC+SXZjo5TeebN_VScALkJKDhLw@mail.gmail.com>
Date: Mon, 23 Jul 2012 00:40:41 +0200
To: "Olivier Cornu" <o.cornu@gmail.com>, "gpsd-dev" <gpsd-dev@nongnu.org>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-4
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Message-ID: <1St4pN-07Y1Eu0@fwd51.aul.t-online.de>
X-ID: b71bguZDYh1xGiadWDs5jLjn-QGpNALDAIIHBYNRG9ytm8YBVPo5mZ9SF0q1UpiZzX@t-dialin.net
X-TOI-MSGID: 8c1d15cb-95a1-49a8-8dbe-de6cc2516d19
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.82
Subject: Re: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 22:40:56 -0000

Hallo,

i may have introduced a bug a bug with that  commit 1ee8e4d601d: Move nowait out of gpsd_add_device.

-#ifdef FORCE_NOWAIT
     (void)ntpshm_init(&context, true);
-#else
-    (void)ntpshm_init(&context, nowait);
-#endif /* FORCE_NOWAIT */

It look for me now, that i have removed the wrong side of the #ifdef.

I will investigate this, and commit a patch soon.

Reinhard

-----Original-Nachricht-----
Von: Olivier Cornu <o.cornu@gmail.com>
An: gpsd-dev <gpsd-dev@nongnu.org>
Cc: Reinhard.Arlt@t-online.de
Betreff: Master branch fails valgrind audit
Datum: Sun, 22 Jul 2012 21:17:33 +0200

The master branch currently fails the valgrind audit with:

$ scons -c && scons && scons valgrind-audit
(...)
gpsd:WARN: exiting.
==2037==
==2037== HEAP SUMMARY:
==2037==     in use at exit: 272 bytes in 1 blocks
==2037==   total heap usage: 65 allocs, 64 frees, 11,690 bytes allocated
==2037==
==2037== 272 bytes in 1 blocks are possibly lost in loss record 1 of 1
==2037==    at 0x4C29DB4: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2037==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==2037==    by 0x559CABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==2037==    by 0x40810B: ntpd_link_activate (in /home/olivier/dev/gpsd/gpsd)
==2037==    by 0x407396: gpsd_add_device (in /home/olivier/dev/gpsd/gpsd)
==2037==    by 0x403A68: main (in /home/olivier/dev/gpsd/gpsd)
==2037==
==2037==
==2037== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ----
==2037== LEAK SUMMARY:
==2037==    definitely lost: 0 bytes in 0 blocks
==2037==    indirectly lost: 0 bytes in 0 blocks
==2037==      possibly lost: 272 bytes in 1 blocks
==2037==    still reachable: 0 bytes in 0 blocks
==2037==         suppressed: 0 bytes in 0 blocks
==2037==
==2037== For counts of detected and suppressed errors, rerun with: -v
==2037== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
scons: done building targets.

I've bisected the issue back to commit 1ee8e4d601d: Move nowait out of
gpsd_add_device.
I haven't investigated any further.

Most likely, this has gone unnoticed thanks to bug #36919 [1]: "scons
valgrind-audit" does not audit local freshly-built gpsd instance.


Regards,

--
Olivier Cornu

[1] https://savannah.nongnu.org/bugs/?36919




From MAILER-DAEMON Mon Jul 23 17:28:10 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1StQAk-00025N-Ea
	for mharc-gpsd-dev@gnu.org; Mon, 23 Jul 2012 17:28:10 -0400
Received: from eggs.gnu.org ([208.118.235.92]:37414)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alvaro.gamez@hazent.com>) id 1StErn-000764-1I
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 05:23:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alvaro.gamez@hazent.com>) id 1StEri-0007Eh-1Z
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 05:23:50 -0400
Received: from mail-we0-f173.google.com ([74.125.82.173]:42515)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alvaro.gamez@hazent.com>) id 1StErh-0007ER-SH
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 05:23:45 -0400
Received: by weyz53 with SMTP id z53so4163951wey.4
	for <gpsd-dev@nongnu.org>; Mon, 23 Jul 2012 02:23:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=from:to:cc:subject:date:message-id:x-mailer:x-gm-message-state;
	bh=tVIi6aoRKw5GYDl82UfioMFyfEH8PrRe+drS2QmYDNk=;
	b=njLRZi+1XKQ8DrMgO7navHzRcJBqiqgEo+3RUOMdcucjvJgA5q43/IWHEAwqUxtRoc
	8RuGI5kPz8aGmKN6uDCkyb2p4L7zOjZOxhHfGRyUPAn13/VW+q4rrOKSoWMysYTWYaCS
	3cYLTz4AmP2AYrxe1PwSNU9UAQugXZbE6IcXwaeDzHEFjLrTcU8jTOUJ0xsK1D9nrxcy
	tXTb7PTXfSrYnKzdOXELy8yVzVD00+Hretg0mL3MBT7gxynyboK/ODzbO+ZJSxXYkdQW
	ogfKCpUgE11saLZuGWtKPviXCbPSuleDkC3ukCD6DX9ek1I1PYhL7N46sJq+d8ARE/TK
	m55g==
Received: by 10.216.3.85 with SMTP id 63mr3900309weg.134.1343035424130;
	Mon, 23 Jul 2012 02:23:44 -0700 (PDT)
Received: from collins.gmr.ssr.upm.es (collins.gmr.ssr.upm.es. [138.4.36.7])
	by mx.google.com with ESMTPS id h9sm16042832wiz.1.2012.07.23.02.23.43
	(version=TLSv1/SSLv3 cipher=OTHER);
	Mon, 23 Jul 2012 02:23:43 -0700 (PDT)
From: "Alvaro G. M" <alvaro.gamez@hazent.com>
To: gpsd-dev@nongnu.org
Date: Mon, 23 Jul 2012 11:23:30 +0200
Message-Id: <1343035410-1894-1-git-send-email-alvaro.gamez@hazent.com>
X-Mailer: git-send-email 1.7.10.4
X-Gm-Message-State: ALoCoQmVjQ+AkUdL7SisJNN8kdYVG9Adpw7SJxrEeV9lBNAMrjM78ANOVUydwPL9vyAyRx1sySfr
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 74.125.82.173
X-Mailman-Approved-At: Mon, 23 Jul 2012 17:28:09 -0400
Subject: [gpsd-dev] [PATCH] Fix compilation error when FIXED_STOP_BITS is set
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 09:23:56 -0000

From: "Alvaro G. M" <alvaro.gamez@hazent.com>

---
 serial.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/serial.c b/serial.c
index 55eaef6..24ef567 100644
--- a/serial.c
+++ b/serial.c
@@ -558,7 +558,7 @@ bool gpsd_next_hunt_setting(struct gps_device_t * session)
 #endif /* FIXED_PORT_SPEED */
 		       session->gpsdata.dev.parity,
 #ifdef FIXED_STOP_BITS
-		       FIXED_STOP_BITS,
+		       FIXED_STOP_BITS
 #else
 		       session->gpsdata.dev.stopbits
 #endif /* FIXED_STOP_BITS */
-- 
1.7.10.4



From MAILER-DAEMON Mon Jul 23 19:00:52 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1StRcS-0005sz-Ig
	for mharc-gpsd-dev@gnu.org; Mon, 23 Jul 2012 19:00:52 -0400
Received: from eggs.gnu.org ([208.118.235.92]:50590)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StRcQ-0005sG-Bg
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 19:00:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StRcO-0001vO-5J
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 19:00:50 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:52234)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StRcO-0001v6-1l
	for gpsd-dev@nongnu.org; Mon, 23 Jul 2012 19:00:48 -0400
Received: by yenl1 with SMTP id l1so6191422yen.4
	for <gpsd-dev@nongnu.org>; Mon, 23 Jul 2012 16:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=qYQ49eKFSR0U+ldWeDt6J8Od61ULDMnvPEYzVPY0xvw=;
	b=AqgWpde0HvtxTkHlpbxdC5gy0YXc3wnVM8GHHBJ1vELV3rqEhqlPJ2zMvtAXo/Fqgj
	2GCZg4w6wMvKa0MlswW3/DzmBnLQSoGlZrROX+q1kiwkKC9lT0RyWhVPdiOiIDKoFfW8
	KPbkZdOePGmKu+Lf2zb5768FRcLsVgP2ZSbhXMWcPNS8ZFe/WZg2+Fs/mbRYnyaJ5PvM
	79VxYDWOjNSVT4CF8/cAJqQ6BWYrnH8R8XX0vInJfP7Ae57l7wfEeYtRm0sMIrlB751n
	3uO5AXuGrmpApxLR9pDtDcRrJcCQHTSjDTTOMrASaXLSaMtOJZZCiq01RbCwUfDdfLjO
	A7aA==
Received: by 10.236.183.198 with SMTP id q46mr16273822yhm.107.1343084447155;
	Mon, 23 Jul 2012 16:00:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Mon, 23 Jul 2012 16:00:26 -0700 (PDT)
In-Reply-To: <1St4pN-07Y1Eu0@fwd51.aul.t-online.de>
References: <CAFLV7-wras2OUqd-GOqupbbeC+SXZjo5TeebN_VScALkJKDhLw@mail.gmail.com>
	<1St4pN-07Y1Eu0@fwd51.aul.t-online.de>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Tue, 24 Jul 2012 01:00:26 +0200
Message-ID: <CAFLV7-zKXtLkGaEh-TRfryVAT248iJ-Ax61ZKQPwJ205Y1XUdw@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.173
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 23:00:51 -0000

Fixed by 2a07669e092555825b905fb91057277b965c7b6b.


From MAILER-DAEMON Tue Jul 24 06:30:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1StcNe-00089K-7Z
	for mharc-gpsd-dev@gnu.org; Tue, 24 Jul 2012 06:30:18 -0400
Received: from eggs.gnu.org ([208.118.235.92]:59769)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1StcNW-00087a-3e
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 06:30:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1StcNV-0003vl-0M
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 06:30:10 -0400
Received: from mailout08.t-online.de ([194.25.134.20]:57747)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1StcNU-0003u2-Pp
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 06:30:08 -0400
Received: from fwd12.aul.t-online.de (fwd12.aul.t-online.de )
	by mailout08.t-online.de with smtp 
	id 1StcNQ-0003eQ-PA; Tue, 24 Jul 2012 12:30:04 +0200
Received: from localhost
	(V8YCOBZY8hcXmzemnH104iVOkMRviwRUBBKf4ZXDjpM1EuBnhOHWMIROOvMB7YYgyQ@[172.20.101.250])
	by fwd12.aul.t-online.de
	with esmtp id 1StcNP-1btQXY0; Tue, 24 Jul 2012 12:30:03 +0200
MIME-Version: 1.0
Received: from 89.182.226.211:59172 by cmpweb58.aul.t-online.de with
	HTTP/1.1 (NGCS V4-0-6-4 on API V3-11-12-2)
In-Reply-To: <CAFLV7-zKXtLkGaEh-TRfryVAT248iJ-Ax61ZKQPwJ205Y1XUdw@mail.gmail.com>
References: <CAFLV7-zKXtLkGaEh-TRfryVAT248iJ-Ax61ZKQPwJ205Y1XUdw@mail.gmail.com>
Date: Tue, 24 Jul 2012 12:30:03 +0200
To: "Olivier Cornu" <o.cornu@gmail.com>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-4
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Message-ID: <1StcNP-1btQXY0@fwd12.aul.t-online.de>
X-ID: V8YCOBZY8hcXmzemnH104iVOkMRviwRUBBKf4ZXDjpM1EuBnhOHWMIROOvMB7YYgyQ@t-dialin.net
X-TOI-MSGID: 4e16a914-5890-46b9-9a7c-a9e9ee3fa803
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.20
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 10:30:16 -0000

Hello,

thank you for your hint,
and the hint, how to make valgrind work again.

Reinhard

-----Original-Nachricht-----
Von: Olivier Cornu <o.cornu@gmail.com>
An: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Betreff: Re: Master branch fails valgrind audit
Datum: Tue, 24 Jul 2012 01:00:26 +0200

Fixed by 2a07669e092555825b905fb91057277b965c7b6b.




From MAILER-DAEMON Tue Jul 24 13:48:36 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1StjDo-00052L-SC
	for mharc-gpsd-dev@gnu.org; Tue, 24 Jul 2012 13:48:36 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39152)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StjDm-00050g-9q
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 13:48:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StjDg-00087f-JO
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 13:48:34 -0400
Received: from mail-yw0-f45.google.com ([209.85.213.45]:34251)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1StjDg-00087b-FT
	for gpsd-dev@nongnu.org; Tue, 24 Jul 2012 13:48:28 -0400
Received: by yhpp34 with SMTP id p34so7032410yhp.4
	for <gpsd-dev@nongnu.org>; Tue, 24 Jul 2012 10:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=Y71nB+abfjuQGdOadpFMD7KZ9//fSHgf1z6MuN79roE=;
	b=VsHsEgNHVhb2X85xiyuHKNXryd/5DPjRSNGTwILK7+mOkI0JGVSknMKRB1X5cTcEDu
	EGtcWuE7AGK0BN57aK+IaIfw/BMZZhw3W3DUNnRlUol9JrRIDjoHF5KYqODDjeGwzsQG
	5N97mQ+vrzqmv5Qf8ix0rZ7jF2wGXJkTnjRfvXJVbY3uHZR211MidkDWUTTGVnKxptVp
	7KvopxNeDBREmMUJSRh5y34JnkLwukf+lKccnVY16iW1QbX5bP+khBsD+4c8YT+obeL7
	J7pR1ExOxYMVNugRuj3ib4VoqDzvPUAFiUfikgyEEFbBASQjrkDHsfk/tt9ZWjra4RA5
	DZzg==
Received: by 10.236.114.200 with SMTP id c48mr15254348yhh.118.1343152107900;
	Tue, 24 Jul 2012 10:48:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Tue, 24 Jul 2012 10:48:07 -0700 (PDT)
In-Reply-To: <1StcNP-1btQXY0@fwd12.aul.t-online.de>
References: <CAFLV7-zKXtLkGaEh-TRfryVAT248iJ-Ax61ZKQPwJ205Y1XUdw@mail.gmail.com>
	<1StcNP-1btQXY0@fwd12.aul.t-online.de>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Tue, 24 Jul 2012 19:48:07 +0200
Message-ID: <CAFLV7-w09c5tRQ5EfLdJ=Rn2vH3eaMxWLz0sZSpGdOEFzHj3jA@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.213.45
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 17:48:35 -0000

On Tue, Jul 24, 2012 at 12:30 PM, Reinhard.Arlt@t-online.de
<Reinhard.Arlt@t-online.de> wrote:
> thank you for your hint,
> and the hint, how to make valgrind work again.

You're welcome: thank you for posting this fix so quick.

--
Olivier


From MAILER-DAEMON Wed Jul 25 16:34:16 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Su8Hg-0007Uz-DE
	for mharc-gpsd-dev@gnu.org; Wed, 25 Jul 2012 16:34:16 -0400
Received: from eggs.gnu.org ([208.118.235.92]:37194)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1Su8Hd-0007Ur-UQ
	for gpsd-dev@nongnu.org; Wed, 25 Jul 2012 16:34:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1Su8Hc-00082L-Rt
	for gpsd-dev@nongnu.org; Wed, 25 Jul 2012 16:34:13 -0400
Received: from mail.recluse.de ([217.196.146.213]:40051)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1Su8Hc-00082B-LK
	for gpsd-dev@nongnu.org; Wed, 25 Jul 2012 16:34:12 -0400
Received: from mail.recluse.de (localhost [127.0.0.1])
	by mail.recluse.de (Postfix) with ESMTP id 7AA4128066;
	Wed, 25 Jul 2012 22:34:09 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at recluse.de
Received: from mail.recluse.de ([127.0.0.1])
	by mail.recluse.de (mail.recluse.de [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id siSPWxUOqOT8; Wed, 25 Jul 2012 22:34:08 +0200 (CEST)
Received: from think.bzed.org (188-192-189-117-dynip.superkabel.de
	[188.192.189.117])
	by mail.recluse.de (Postfix) with ESMTPSA id D087F28035;
	Wed, 25 Jul 2012 22:34:07 +0200 (CEST)
Message-ID: <5010583F.3090008@bzed.de>
Date: Wed, 25 Jul 2012 22:34:07 +0200
From: Bernd Zeimetz <bernd@bzed.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.5) Gecko/20120624 Icedove/10.0.5
MIME-Version: 1.0
To: gpsd-dev@nongnu.org
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 217.196.146.213
Subject: [gpsd-dev] www/cansetup - ship in tarball / documentation?
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 20:34:15 -0000

Hi,

I've seen www/cansetup in the repository. There are two things which could be
improved here in my opinion:

- stuff in www is not shipped in the tarball. I think it should be shipped with
the next release as example/documentation for setting up a can bus device.

- it completely lacks a proper documentation :) Maybe I've missed it, but some
documentation which explains how to connect such a device and so on :)

Cheers,

Bernd
-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


From MAILER-DAEMON Thu Jul 26 04:01:03 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SuJ0J-00031Q-2Z
	for mharc-gpsd-dev@gnu.org; Thu, 26 Jul 2012 04:01:03 -0400
Received: from eggs.gnu.org ([208.118.235.92]:56525)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SuJ0D-00030e-SG
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 04:01:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SuJ08-0003dO-5x
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 04:00:57 -0400
Received: from mailout08.t-online.de ([194.25.134.20]:58063)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Reinhard.Arlt@t-online.de>) id 1SuJ07-0003dI-Ut
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 04:00:52 -0400
Received: from fwd25.aul.t-online.de (fwd25.aul.t-online.de )
	by mailout08.t-online.de with smtp 
	id 1SuJ06-00067s-8r; Thu, 26 Jul 2012 10:00:50 +0200
Received: from localhost
	(GvpeQOZpohtOgiCutaqcdTdSfvN9dURncTaiOZHom-hEBAt1+viT446ymWQyvzLZjL@[172.20.101.250])
	by fwd25.aul.t-online.de
	with esmtp id 1SuJ01-0J1OlM0; Thu, 26 Jul 2012 10:00:45 +0200
MIME-Version: 1.0
Received: from 93.218.116.219:47181 by cmpweb12.aul.t-online.de with
	HTTP/1.1 (NGCS V4-0-6-4 on API V3-11-12-2)
Date: Thu, 26 Jul 2012 10:00:45 +0200
To: "gpsd-dev" <gpsd-dev@nongnu.org>
X-Priority: 3
X-UMS: email
X-Mailer: DTAG NGCS V4-0-6-4
From: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Message-ID: <1SuJ01-0J1OlM0@fwd25.aul.t-online.de>
X-ID: GvpeQOZpohtOgiCutaqcdTdSfvN9dURncTaiOZHom-hEBAt1+viT446ymWQyvzLZjL@t-dialin.net
X-TOI-MSGID: 0b85089c-d73e-4f89-ac89-3aaaa9e357cd
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 194.25.134.20
Subject: [gpsd-dev] Tool to view AIS data
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 08:01:02 -0000

Hello,

is there a simple tool to display the ais data from gpsd?

Thank you

Reinhard





From MAILER-DAEMON Thu Jul 26 05:59:39 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SuKr5-0001t4-UN
	for mharc-gpsd-dev@gnu.org; Thu, 26 Jul 2012 05:59:39 -0400
Received: from eggs.gnu.org ([208.118.235.92]:47017)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1SuKqz-0001pr-Fb
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 05:59:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1SuKqv-0007Sy-B7
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 05:59:33 -0400
Received: from mailx.techworks.ie ([88.198.36.49]:57906)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1SuKqv-0007Sl-4n
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 05:59:29 -0400
Received: from localhost (localhost [127.0.0.1])
	by mailx.techworks.ie (Postfix) with ESMTP id 7857C608574
	for <gpsd-dev@nongnu.org>; Thu, 26 Jul 2012 10:59:24 +0100 (IST)
X-Virus-Scanned: amavisd-new at techworks.ie
Received: from mailx.techworks.ie ([127.0.0.1])
	by localhost (mailx.techworks.ie [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YbpAPxt4Awyh for <gpsd-dev@nongnu.org>;
	Thu, 26 Jul 2012 10:59:23 +0100 (IST)
Received: from [192.168.5.183] (unknown [86.43.120.173])
	by mailx.techworks.ie (Postfix) with ESMTPSA id 752B8608563
	for <gpsd-dev@nongnu.org>; Thu, 26 Jul 2012 10:59:23 +0100 (IST)
Message-ID: <50111546.5060903@techworks.ie>
Date: Thu, 26 Jul 2012 11:00:38 +0100
From: Christian Gagneraud <chris@techworks.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: gpsd-dev@nongnu.org
References: <1SuJ01-0J1OlM0@fwd25.aul.t-online.de>
In-Reply-To: <1SuJ01-0J1OlM0@fwd25.aul.t-online.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 88.198.36.49
Subject: Re: [gpsd-dev] Tool to view AIS data
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 09:59:39 -0000

On 26/07/12 09:00, Reinhard.Arlt@t-online.de wrote:
> Hello,
>
> is there a simple tool to display the ais data from gpsd?

What do you mean by display? Isn't the JSON output enough?
Do you want to display vessels on a map?
There's as well an AIS python parser in devtools that can output a more 
human friendly text.

Chris

>
> Thank you
>
> Reinhard
>
>
>
>


-- 
Christian Gagneraud,
Embedded systems engineer.
Techworks Marine
1 Harbour road
Dun Laoghaire
Co. Dublin
Ireland
Tel: + 353 (0) 1 236 5990
Web: http://www.techworks.ie/




From MAILER-DAEMON Thu Jul 26 11:11:02 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SuPiQ-0007PP-03
	for mharc-gpsd-dev@gnu.org; Thu, 26 Jul 2012 11:11:02 -0400
Received: from eggs.gnu.org ([208.118.235.92]:37464)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SuPiN-0007Nq-NB
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 11:11:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SuPiH-0007fT-SY
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 11:10:59 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:36392 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1SuPiH-0007fP-Ol
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 11:10:53 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id A55034067B; Thu, 26 Jul 2012 11:10:41 -0400 (EDT)
Date: Thu, 26 Jul 2012 11:10:41 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Message-ID: <20120726151041.GD23171@thyrsus.com>
References: <1SuJ01-0J1OlM0@fwd25.aul.t-online.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1SuJ01-0J1OlM0@fwd25.aul.t-online.de>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Tool to view AIS data
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 15:11:00 -0000

Reinhard.Arlt@t-online.de <Reinhard.Arlt@t-online.de>:
> is there a simple tool to display the ais data from gpsd?

xgps will do it.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Thu Jul 26 14:25:44 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SuSkq-0007FA-Py
	for mharc-gpsd-dev@gnu.org; Thu, 26 Jul 2012 14:25:44 -0400
Received: from eggs.gnu.org ([208.118.235.92]:48201)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1SuSko-0007F4-Um
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 14:25:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1SuSkn-00011g-RF
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 14:25:42 -0400
Received: from mail.recluse.de ([217.196.146.213]:46823)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernd@bzed.de>) id 1SuSkn-00011B-Jz
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 14:25:41 -0400
Received: from mail.recluse.de (localhost [127.0.0.1])
	by mail.recluse.de (Postfix) with ESMTP id 9AF7928083;
	Thu, 26 Jul 2012 20:25:39 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at recluse.de
Received: from mail.recluse.de ([127.0.0.1])
	by mail.recluse.de (mail.recluse.de [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id nFc7oZ8ooEr8; Thu, 26 Jul 2012 20:25:38 +0200 (CEST)
Received: from think.bzed.org (188-192-189-117-dynip.superkabel.de
	[188.192.189.117])
	by mail.recluse.de (Postfix) with ESMTPSA id E429A27F4C;
	Thu, 26 Jul 2012 20:25:37 +0200 (CEST)
Message-ID: <50118BA1.1090002@bzed.de>
Date: Thu, 26 Jul 2012 20:25:37 +0200
From: Bernd Zeimetz <bernd@bzed.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.5) Gecko/20120624 Icedove/10.0.5
MIME-Version: 1.0
To: Simon Dawson <spdawson@gmail.com>
References: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
In-Reply-To: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 217.196.146.213
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] ARM/uClibc build problem
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 18:25:44 -0000

Hi,


On 07/21/2012 11:36 AM, Simon Dawson wrote:
> Using Buildroot, I'm cross compiling gpsd 3.7 for ARM, using uClibc.
> The build is falling over with the following error.
> 
>   gpsmon.o: In function `monitor_fixframe':
>   gpsmon.c:(.text+0x264): undefined reference to `acs_map'
>   monitor_nmea.o: In function `nmea_update':
>   monitor_nmea.c:(.text+0xbc0): undefined reference to `acs_map'
>   collect2: ld returned 1 exit status
>   scons: *** [gpsmon] Error 1
>   scons: building terminated because of errors.

please

- send a full output of your build (that issue should not happen...)
- try to add -lncurses -ltinfo to the linker call which tries to link gpsmon
(assuming you have ncurses available - thats why I need your build output :)


Cheers,

Bernd

-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


From MAILER-DAEMON Thu Jul 26 16:11:57 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SuUPd-0004YE-CS
	for mharc-gpsd-dev@gnu.org; Thu, 26 Jul 2012 16:11:57 -0400
Received: from eggs.gnu.org ([208.118.235.92]:40481)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <perezmeyer@gmail.com>) id 1SuUPa-0004WP-Cg
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 16:11:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <perezmeyer@gmail.com>) id 1SuUPY-00085d-U8
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 16:11:54 -0400
Received: from mail-gg0-f173.google.com ([209.85.161.173]:42757)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <perezmeyer@gmail.com>)
	id 1SuUPY-00085W-Pp; Thu, 26 Jul 2012 16:11:52 -0400
Received: by ggnp1 with SMTP id p1so2386078ggn.4
	for <multiple recipients>; Thu, 26 Jul 2012 13:11:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:subject:date:user-agent:cc:references:in-reply-to
	:mime-version:content-type:content-transfer-encoding:message-id;
	bh=8JthdF5WM1Ad/u/Tofolu/lFlvH5vbK9+AOPEXQ/iyw=;
	b=QSjMTAxb5yhdowl7aSejHC+G8qSsg9r3WLSlVY80ASJ31OFeHA9+dbNwWPkPmN+2Hx
	ELwiFhv6O8shCMCq4dBcgOEq9qcq5szVALR8sw3ZxmUXPzMRa5jpsNqBObviJrpg2v83
	JLbMnMNPTR9hcAefxC+voZJz5P8qZQWI/aeG7jNzROlcBjud/emI+8puGE+yN7jwiPay
	wGlatJsFrTAiUl48rSuNO8A5PyYvHkAkFtRIe5Su4XGZB66g+IBni7knZT/SsnfctC+x
	xNSSkbvQnoEqNgh6MUzq8h8kRT7h08vA0P/kYk5SkLLi0Gb+ktZCPS5l3AvM/RRAsfqn
	LUYw==
Received: by 10.101.6.32 with SMTP id j32mr4123260ani.82.1343333511957;
	Thu, 26 Jul 2012 13:11:51 -0700 (PDT)
Received: from luna.localnet ([190.97.25.23])
	by mx.google.com with ESMTPS id e19sm195011ann.10.2012.07.26.13.11.49
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 26 Jul 2012 13:11:51 -0700 (PDT)
From: Lisandro =?iso-8859-1?q?Dami=E1n_Nicanor_P=E9rez_Meyer?=
	<perezmeyer@gmail.com>
To: gpsd-dev@nongnu.org,
 tom@kera.name
Date: Thu, 26 Jul 2012 17:11:37 -0300
User-Agent: KMail/1.13.7 (Linux/3.2.21+edid; KDE/4.8.4; x86_64; ; )
References: <201207251410.37872.perezmeyer@gmail.com>
	<50118B77.5050102@kera.name>
In-Reply-To: <50118B77.5050102@kera.name>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1373013.pqGincMYl7";
	protocol="application/pgp-signature"; micalg=pgp-sha256
Content-Transfer-Encoding: 7bit
Message-Id: <201207261711.46547.perezmeyer@gmail.com>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.161.173
Cc: gpsd-users@nongnu.org
Subject: Re: [gpsd-dev] [gpsd-users] Setting the time via NTP
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 20:11:55 -0000

--nextPart1373013.pqGincMYl7
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Jue 26 Jul 2012 15:24:55 Tomalak Geret'kal escribi=F3:
[snip]=20
> You need to investigate more how to configure ntpd. By
> default it ignores large time offsets.. and that, well, that
> is a large time offset! Look at the "tinker" config settings
> in particular. You might find chrony more appropriate here.

Indeed, that seems to be the problem. Thanks!

=2D-=20
Gabardinas "Windows 95". Se cuelgan solas.

Lisandro Dami=E1n Nicanor P=E9rez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

--nextPart1373013.pqGincMYl7
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAABCAAGBQJQEaR6AAoJEKtkX0BihqfQzE8QALezhYiDA+pkFATnh3lfoggs
jFtgAOWKSL8P6O2u5EfW3tqSGQMIjE9QhBNC5kp9Zq7razkjhN+tL3PbiZmU+wzn
IUSI0VFyTUzDyhkgsgqbRDfZgRe1Oj38kYFyxmmRk6+/JQX2m4wJKFS949sGGG/X
xWWY1+9Mf5Jp26ADzpAlrt/bpQfmc0vrKCcntqE8lj4rse9vQv2lBUej29UoWXs7
AZwzYlIt0NpcG2FRR53COfsQQZx4i4/CQmIVOwkUjGt1/IouCIyS1AN+EnAFrWsF
ReM+wEzLZKi5nlG55ns2Y8Pi5j/r0GHWtz3W+ky2rkZVDvArC8bDR8hR8lVQmrwL
mv3+qvFbMM4WxO4EPcNfm5M1ePqAQ0HpPaRPa1dTx6cOf0uBn9D3BhjF4LSMGFs4
4uMqfSOHe90pdtPk20cjj9tLiAQrhak3vdotvLijZn7Xzsb06VMdVMorAk3CJC4f
W730DCw4lCsmGlN2la1ZmvnwakWLfmJr486pbXNh1MkBwgT5HeFK/pi2gaZN7erK
LJh3ncCMq9d1qQRHFCXJIXY98c+UZROFuWnv6T9496ykYYkJgOJbGSTgnOidovd4
YzqgM3y+yklM9EZI/xEAhOzGWacCZ5ho3nBxQ3KBMQathgj4/NILRBVTtYMV+EY9
pm+9MrzWJbHW8Paz2bud
=rD1B
-----END PGP SIGNATURE-----

--nextPart1373013.pqGincMYl7--


From MAILER-DAEMON Fri Jul 27 09:40:40 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SukmW-0004gt-6F
	for mharc-gpsd-dev@gnu.org; Fri, 27 Jul 2012 09:40:40 -0400
Received: from eggs.gnu.org ([208.118.235.92]:39742)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1SubF6-0001tZ-BW
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 23:29:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1SubF5-0004Ex-BB
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 23:29:32 -0400
Received: from mail-ob0-f173.google.com ([209.85.214.173]:51326)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1SubF5-0004Em-5s
	for gpsd-dev@nongnu.org; Thu, 26 Jul 2012 23:29:31 -0400
Received: by obbta14 with SMTP id ta14so3444630obb.4
	for <gpsd-dev@nongnu.org>; Thu, 26 Jul 2012 20:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=n6EtKBvzAB1UBjZhpfhpFKOD+nC6IsSLscGkpra1Y3Y=;
	b=wv/0e5g1I+KPkuF6l7AqWKqh7sJss0Bapi2Yy0iebOgc+QT65FAKlTgel/X7cVeTji
	ZxtHerM0BeTHVJNNHxT8/oNK1qPSYA8+Y11ts/BIji4Qa9p13KTMeir+qYV10EAw9a5P
	tY2dszvECuq+9WM3OWP87vcz73oWDhXAQEig9lhYyngAqTh/2bzLfKq8+P7kz2ggR16X
	nzY26FRfwGJ39KO3Xd5MyhZ3lMuDjZJ8cex8HjukIc0wrUUqXMUIE9w2vh6kAStit9/w
	0XudcPmbP2+cHGrtDqA3wD8s1RiKHjsBo6SrmFEG8RkL+xnJL2Kn5rGvqd2lQK33a15p
	pcYA==
Received: by 10.182.144.68 with SMTP id sk4mr1615640obb.0.1343359770347; Thu,
	26 Jul 2012 20:29:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.7.228 with HTTP; Thu, 26 Jul 2012 20:29:10 -0700 (PDT)
From: KIU Shueng Chuan <nixchuan@gmail.com>
Date: Fri, 27 Jul 2012 11:29:10 +0800
Message-ID: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.214.173
X-Mailman-Approved-At: Fri, 27 Jul 2012 09:40:38 -0400
Subject: [gpsd-dev] devtools/ais.py type25 parsing bug
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 03:29:33 -0000

Hi,

In devtools/ais.py from gpsd release 3.7, the bitfield definition of
"type25" is causing a TypeError exception in aivdm_unpack().

type25 = {
    bitfield("addressed", ...),
    bitfield("structured", ..."Dimension to Bow"),     # legend field
should be "Binary Data Flag"
    ...
    bitfield("data", None, ...)                                 #
width field set to None causes the exception
}

One of the last few lines of aivdm_unpack() does
offset += inst.width
which chokes on width==None

Changing None to 0 in the bitfield definition makes it work.



For reference, the following was the sentence that triggered it:
!AIVDM,1,1,,B,I9NS<Lh01dWK:UN0bOM2MR2d0<<K,0*58


From MAILER-DAEMON Fri Jul 27 10:48:15 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sulpv-000289-Ek
	for mharc-gpsd-dev@gnu.org; Fri, 27 Jul 2012 10:48:15 -0400
Received: from eggs.gnu.org ([208.118.235.92]:49678)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1Sulpn-00026x-W8
	for gpsd-dev@nongnu.org; Fri, 27 Jul 2012 10:48:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1Sulpi-0000HP-3Z
	for gpsd-dev@nongnu.org; Fri, 27 Jul 2012 10:48:07 -0400
Received: from mailx.techworks.ie ([88.198.36.49]:53566)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@techworks.ie>) id 1Sulph-0000H9-TJ
	for gpsd-dev@nongnu.org; Fri, 27 Jul 2012 10:48:02 -0400
Received: from localhost (localhost [127.0.0.1])
	by mailx.techworks.ie (Postfix) with ESMTP id D9308608908
	for <gpsd-dev@nongnu.org>; Fri, 27 Jul 2012 15:47:59 +0100 (IST)
X-Virus-Scanned: amavisd-new at techworks.ie
Received: from mailx.techworks.ie ([127.0.0.1])
	by localhost (mailx.techworks.ie [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lYcoQzb8vVl7 for <gpsd-dev@nongnu.org>;
	Fri, 27 Jul 2012 15:47:59 +0100 (IST)
Received: from [192.168.5.183] (unknown [86.43.120.173])
	by mailx.techworks.ie (Postfix) with ESMTPSA id D63C0608903
	for <gpsd-dev@nongnu.org>; Fri, 27 Jul 2012 15:47:58 +0100 (IST)
Message-ID: <5012AA1D.8010802@techworks.ie>
Date: Fri, 27 Jul 2012 15:47:57 +0100
From: Christian Gagneraud <chris@techworks.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: gpsd-dev@nongnu.org
References: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
In-Reply-To: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3)
X-Received-From: 88.198.36.49
Subject: Re: [gpsd-dev] devtools/ais.py type25 parsing bug
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 14:48:13 -0000

On 27/07/12 04:29, KIU Shueng Chuan wrote:
> Hi,
>
> In devtools/ais.py from gpsd release 3.7, the bitfield definition of
> "type25" is causing a TypeError exception in aivdm_unpack().
>
> type25 = {
>      bitfield("addressed", ...),
>      bitfield("structured", ..."Dimension to Bow"),     # legend field
> should be "Binary Data Flag"
>      ...
>      bitfield("data", None, ...)                                 #
> width field set to None causes the exception
> }
>
> One of the last few lines of aivdm_unpack() does
> offset += inst.width
> which chokes on width==None
>
> Changing None to 0 in the bitfield definition makes it work.

Hi Kiu,

Thanks for pointing that out. I will fix that shortly.
Please note, that the gpsd program itself handle this sentence correctly.

Any reason you are using devtools/ais.py?
This script has not been tested as thoroughly as gpsd.
If you want a sand alone stdin-to-stdout decoder use gpsdecode instead.


> For reference, the following was the sentence that triggered it:
> !AIVDM,1,1,,B,I9NS<Lh01dWK:UN0bOM2MR2d0<<K,0*58
>

Chris

-- 
Christian Gagneraud,
Embedded systems engineer.
Techworks Marine
1 Harbour road
Dun Laoghaire
Co. Dublin
Ireland
Tel: + 353 (0) 1 236 5990
Web: http://www.techworks.ie/




From MAILER-DAEMON Sat Jul 28 17:13:22 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SvEKA-0002oZ-Nk
	for mharc-gpsd-dev@gnu.org; Sat, 28 Jul 2012 17:13:22 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60381)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1Sv1io-00060D-JH
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 03:45:59 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1Sv1in-0007Pq-P7
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 03:45:58 -0400
Received: from mail-ob0-f173.google.com ([209.85.214.173]:46629)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nixchuan@gmail.com>) id 1Sv1in-0007PY-KT
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 03:45:57 -0400
Received: by obbta14 with SMTP id ta14so5218013obb.4
	for <gpsd-dev@nongnu.org>; Sat, 28 Jul 2012 00:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=3Bb1GIkh0NDH92JDZTe7Xu7kct8HZ+ObFbEiURcXOAg=;
	b=Qr94Fd+XhbeF7oFftZDXyvyo1YZUDl2tESxBA1ILb3UsdzbLGprFyog4lQWMS3TrHA
	TBipAvY2FFCxWP9r0qLMLYxU/0OV84xpvKG2k4RIgCspjQ3G4h3LSR4WEZ8BkAUKwxvx
	QADnWhZooaCcsHwW+dc52QCITwzg/qfkE0XgQqyQV6dJ+DX9ackd/0Ls/T36WJWjf+Sj
	iTz2lRtuJ5hOkkme0Uevz63aSyPtJeeJpMOAayDKjcrvu4hdq+e+awMTU9Hq2TyJZUlM
	u4bpCuQO8PEvFMeMyjMR7HLDC9pG/qXmZzy37+IzaC6y6O9ba25SRCYKQltKSubdmhzX
	Likg==
Received: by 10.60.168.230 with SMTP id zz6mr7240153oeb.11.1343461556695; Sat,
	28 Jul 2012 00:45:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.7.228 with HTTP; Sat, 28 Jul 2012 00:45:36 -0700 (PDT)
From: KIU Shueng Chuan <nixchuan@gmail.com>
Date: Sat, 28 Jul 2012 15:45:36 +0800
Message-ID: <CAP2skc8=fuJE0hCr6snvukcXcm+fcHMskLGMz2oOYHza6O9c-g@mail.gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.214.173
X-Mailman-Approved-At: Sat, 28 Jul 2012 17:13:21 -0400
Subject: Re: [gpsd-dev] devtools/ais.py type25 parsing bug
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jul 2012 07:45:59 -0000

Hi Christian,

> Any reason you are using devtools/ais.py?
> This script has not been tested as thoroughly as gpsd.
> If you want a sand alone stdin-to-stdout decoder use gpsdecode instead.

Mainly for the histogram functionality in ais.py.
It runs on Windows too.


From MAILER-DAEMON Sat Jul 28 19:52:37 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1SvGoH-0002TB-PR
	for mharc-gpsd-dev@gnu.org; Sat, 28 Jul 2012 19:52:37 -0400
Received: from eggs.gnu.org ([208.118.235.92]:44517)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SvGoF-0002Sa-PQ
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 19:52:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SvGoE-0001QB-TJ
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 19:52:35 -0400
Received: from mail-gg0-f173.google.com ([209.85.161.173]:40647)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <o.cornu@gmail.com>) id 1SvGoE-0001Q7-Nl
	for gpsd-dev@nongnu.org; Sat, 28 Jul 2012 19:52:34 -0400
Received: by ggnp1 with SMTP id p1so3973728ggn.4
	for <gpsd-dev@nongnu.org>; Sat, 28 Jul 2012 16:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=yFRK91FE1bbmVurWQVPhFovWZyOgkJrx80fZcvyYyPo=;
	b=fpijuy6er4StrKIIWEUqVt8y0Mz7L/UUCMSVyIYpGxxI2JTy2cNrrR5cexlFQo0RML
	anZIWCXzCfcq4Xa41V/bS0E2k79+LgVIe/78qCHU+VKcFnX7j4iX9WGTuz69pJa1i1cl
	YXAHKQnuc0SXp0ZKchubWOOKnvYHR+Qh34kqzIlmT9S+bKDj5EoYn0af5Nd9blqhiVT/
	GBdprZpFDqH/jV695pKVv5s869ajuHkpOkbujrwYvP4eutqATmI8jNMfmSnaRZEp20IO
	ZJTWWkNE84q5Tv6Ng+YL3T8XOKyFD50nxZJJJvJEPlYYTPaJZllZyODeF68og7V4H//o
	xICA==
Received: by 10.236.200.232 with SMTP id z68mr6348489yhn.46.1343519553850;
	Sat, 28 Jul 2012 16:52:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.7 with HTTP; Sat, 28 Jul 2012 16:52:13 -0700 (PDT)
In-Reply-To: <1StcNP-1btQXY0@fwd12.aul.t-online.de>
References: <CAFLV7-zKXtLkGaEh-TRfryVAT248iJ-Ax61ZKQPwJ205Y1XUdw@mail.gmail.com>
	<1StcNP-1btQXY0@fwd12.aul.t-online.de>
From: Olivier Cornu <o.cornu@gmail.com>
Date: Sun, 29 Jul 2012 01:52:13 +0200
Message-ID: <CAFLV7-yyBhDR8V6KN88MXCKzMDc5Tf6Ls=8NM-XpFpHeFTMANA@mail.gmail.com>
To: "Reinhard.Arlt@t-online.de" <Reinhard.Arlt@t-online.de>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.161.173
Cc: gpsd-dev <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Master branch fails valgrind audit
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jul 2012 23:52:36 -0000

Hi again,

On Tue, Jul 24, 2012 at 12:30 PM, Reinhard.Arlt@t-online.de
<Reinhard.Arlt@t-online.de> wrote:
>
> thank you for your hint,
> and the hint, how to make valgrind work again.

If bug #36919 [1] had anything to do with it, would you consider
looking deeper into it and perhaps applying the supplied patch?
Thanks!

--
Olivier Cornu

[1] https://savannah.nongnu.org/bugs/?36919


From MAILER-DAEMON Mon Jul 30 08:23:56 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Svp0u-0004VT-Ab
	for mharc-gpsd-dev@gnu.org; Mon, 30 Jul 2012 08:23:56 -0400
Received: from eggs.gnu.org ([208.118.235.92]:48178)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1Svp0l-0004Ul-Hq
	for gpsd-dev@nongnu.org; Mon, 30 Jul 2012 08:23:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>) id 1Svp0g-0003cf-M9
	for gpsd-dev@nongnu.org; Mon, 30 Jul 2012 08:23:47 -0400
Received: from fnord.ir.bbn.com ([192.1.100.210]:51684)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gdt@ir.bbn.com>)
	id 1Svp0g-0003c0-IW; Mon, 30 Jul 2012 08:23:42 -0400
Received: by fnord.ir.bbn.com (Postfix, from userid 10853)
	id 707D6B0AC; Mon, 30 Jul 2012 08:23:41 -0400 (EDT)
From: Greg Troxel <gdt@ir.bbn.com>
To: Egil <egil.moller@freecode.no>
References: <5015CCB7.3070404@freecode.no>
OpenPGP: id=32611E25
X-Hashcash: 1:20:120730:egil.moller@freecode.no::ewzAh0UZNgom6eHl:000000000000000000000000000000000000000rCB
X-Hashcash: 1:20:120730:gpsd-users@nongnu.org::ewzAh0UZNgom6eHl:00000000000000000000000000000000000000002dY1
X-Hashcash: 1:20:120730:gpsd-dev@nongnu.org::ewzAh0UZNgom6eHl:0000000000000000000000000000000000000000003387
Date: Mon, 30 Jul 2012 08:23:41 -0400
In-Reply-To: <5015CCB7.3070404@freecode.no> (Egil's message of "Mon, 30 Jul
	2012 01:52:23 +0200")
Message-ID: <rmihaspjv3m.fsf@fnord.ir.bbn.com>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 192.1.100.210
Cc: gpsd-dev@nongnu.org, gpsd-users@nongnu.org
Subject: Re: [gpsd-dev] [gpsd-users] Announcement: agpsd - a gpsd logging
	and replication daemon
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 12:23:55 -0000

--=-=-=
Content-Type: text/plain


Egil <egil.moller@freecode.no> writes:

> I hope you will find the following little announcement of a GPSD
> complementary daemon interesting:
>
> I have just finished a beta version of AGPSD, a GPSD logging and
> replication daemon.

You left out two critical pieces of information:

  a link to the source code repository

  saying what the license is

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (NetBSD)

iEYEARECAAYFAlAWfM0ACgkQ+vesoDJhHiX5QwCeKymDlSDyXEuC6VSm5Z7dBxgU
ZWYAnjUdsbrtwx2m14/F0R2PRASIVueR
=AQvd
-----END PGP SIGNATURE-----
--=-=-=--


From MAILER-DAEMON Mon Jul 30 12:46:10 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Svt6g-0006vV-78
	for mharc-gpsd-dev@gnu.org; Mon, 30 Jul 2012 12:46:10 -0400
Received: from eggs.gnu.org ([208.118.235.92]:34596)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <egil.moller@freecode.no>) id 1SvdHi-0002fs-Bi
	for gpsd-dev@nongnu.org; Sun, 29 Jul 2012 19:52:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <egil.moller@freecode.no>) id 1SvdHg-0001IH-OU
	for gpsd-dev@nongnu.org; Sun, 29 Jul 2012 19:52:30 -0400
Received: from mail-lpp01m010-f45.google.com ([209.85.215.45]:53696)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <egil.moller@freecode.no>) id 1SvdHg-0001Hq-GL
	for gpsd-dev@nongnu.org; Sun, 29 Jul 2012 19:52:28 -0400
Received: by lahc1 with SMTP id c1so2909221lah.4
	for <gpsd-dev@nongnu.org>; Sun, 29 Jul 2012 16:52:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:x-enigmail-version:content-type:x-gm-message-state;
	bh=9h/OxDde4Wg7+w+yTC+GvsOJoy8E+ncLuac8aG4bgaw=;
	b=QiC3WlO5eR3e3dsr8+SKLZajWqs9l/JAsInV8miNGCUFKiFjZ3KvEy0A9zjOFxw/Yl
	lqarxTCCNAsAuU5UjDIQgN9qn2TVffFHCGN1eIgzZyh3Ptdg1vz9QLTTP7RwDxAuPzHG
	NKhQNU6D4u9g2afJOW6w4W60MdonMPKBlBfmol13iSDAc/8OGuFCni1qWxLl77Y5oVfT
	D8HP83DWs8jy6UcWt84h1KiGhQ4e2w3BGrAR/T83iIurfS8eY9aYn9Sb6GJiPhGnHQDq
	3/iQ1VVpBeietfDqMmx7cWdAFCv9REoR9p+/0iLKCS4Sz05IdzRPr6wS3ylCRnifFXPK
	yVTw==
Received: by 10.152.148.195 with SMTP id tu3mr9708169lab.16.1343605946756;
	Sun, 29 Jul 2012 16:52:26 -0700 (PDT)
Received: from [37.123.149.45] (h-149-45.a336.priv.bahnhof.se. [37.123.149.45])
	by mx.google.com with ESMTPS id h9sm1836335lbi.9.2012.07.29.16.52.24
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sun, 29 Jul 2012 16:52:25 -0700 (PDT)
Message-ID: <5015CCB7.3070404@freecode.no>
Date: Mon, 30 Jul 2012 01:52:23 +0200
From: Egil <egil.moller@freecode.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: gpsd-users@nongnu.org
X-Enigmail-Version: 1.4.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig1A76294F1AFDDD70AB564E6C"
X-Gm-Message-State: ALoCoQknTuQvKg+vXaB7YlSs5iT5ULRDKscZ2Okw9t62NWexNmX1RcuygZXntLgxt8HtnoPdGJUG
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.215.45
X-Mailman-Approved-At: Mon, 30 Jul 2012 12:46:08 -0400
Cc: gpsd-dev@nongnu.org
Subject: [gpsd-dev] Announcement: agpsd - a gpsd logging and replication
	daemon
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 23:52:31 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1A76294F1AFDDD70AB564E6C
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi!

I hope you will find the following little announcement of a GPSD
complementary daemon interesting:

I have just finished a beta version of AGPSD, a GPSD logging and
replication daemon.

The typical usage of AGPSD is to send GPSD data over a intermittent
network connection from a vehicle to a server, and have the server serve
the last known data as well as history to clients. Currently the data
can be retrieved using the GPSD protocol and KML.

AGPSD works like a GPSD router, with caching. It acts as both a GPSD
client and server, and stores all NMEA events in an SQLite database. In
addition to simply relaying data to clients, it supports replaying old
data, and replication of the log between AGPSD servers.

It can initiate connections for replication both from the receiving and
the sending end, enabling operation over networks with dynamic ip:s

AGPSD also acts as a web server and serves the recorded data as KML, as
well as an OpenLayers based user interface to browse said kml data.

Please let me know if you have any ideas, critique or general comments!

Best regards,
Egil M=C3=B6ller


--------------enig1A76294F1AFDDD70AB564E6C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQFcy3AAoJELvEb9hu4GSLh4QH+wQcGsp4lMrQLW1k018UBS7D
S2/g/EDjVbqp9uAOGrhjP0Qvho1BTJUt0UV4p1BxSTqRSza5z6eqEkJ7VlRppt55
we0s7tSiCeODPrIqIfiiiGbhHfXnx+Iu98ANzPKwvXYFIwQVtHssWYYgW5o95zfy
fjlttrGNvGHpo+WeRg+49Hh1xevHKgmyXK+8KcqDPDc5J75hfDI08URJ5cMTL/4Y
r36Q8OzUddt7tlleDFSGbMFvYeMf+Ct+qd8QUmv0cAZ4pDYXDyV2zn0/EfrxFnoE
jmpXjZJkGP6CWQJxNhcj8WDt/GmfC3F0xBnr10zsbNlNqJnZLZ/J6TWBQ4ka1WY=
=fLYb
-----END PGP SIGNATURE-----

--------------enig1A76294F1AFDDD70AB564E6C--


From MAILER-DAEMON Tue Jul 31 00:09:13 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sw3lh-0001BC-26
	for mharc-gpsd-dev@gnu.org; Tue, 31 Jul 2012 00:09:13 -0400
Received: from eggs.gnu.org ([208.118.235.92]:53207)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3le-0001Ay-KT
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:09:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3ld-0003uU-F7
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:09:10 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:47548 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3ld-0003uO-BC
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:09:09 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id 382FE40556; Tue, 31 Jul 2012 00:09:07 -0400 (EDT)
Date: Tue, 31 Jul 2012 00:09:07 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Ukygerkgubiekd Ukygerkgubiekd <ukyg9e5r6k7gubiekd6@yahoo.com>
Message-ID: <20120731040907.GA15166@thyrsus.com>
References: <1342706333.53559.YahooMailNeo@web142605.mail.bf1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1342706333.53559.YahooMailNeo@web142605.mail.bf1.yahoo.com>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: "gpsd-dev@nongnu.org" <gpsd-dev@nongnu.org>
Subject: Re: [gpsd-dev] Mingw port
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 04:09:11 -0000

Ukygerkgubiekd Ukygerkgubiekd <ukyg9e5r6k7gubiekd6@yahoo.com>:
> However, Windows has a completely different set of APIs for serial comms, and for timing/handshaking/waiting etc.
> 
> To get drivers, the daemon and the regression tests working under Windows hence requires some abstraction layer over those differences.
> 
> My idea is that such a layer could also incorporate the existing differences between shm, dbus, QT, sockets and fds.
> Your comments appreciated!

Sounds useful if done right, but quite ugly and obtrusive if done wrong.

I am, at least, open to refactoring changes that would narrow thw coupling to 
the base OS.  Most of the changes would be in gpsd.c and serial.c, correct?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Tue Jul 31 00:12:41 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sw3p3-0001Mh-Di
	for mharc-gpsd-dev@gnu.org; Tue, 31 Jul 2012 00:12:41 -0400
Received: from eggs.gnu.org ([208.118.235.92]:34206)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3p0-0001MN-TQ
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:12:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3oz-0005Am-Se
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:12:38 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:47564 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3oz-0005Ah-Ob
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:12:37 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id AFF1640556; Tue, 31 Jul 2012 00:12:36 -0400 (EDT)
Date: Tue, 31 Jul 2012 00:12:36 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Simon Dawson <spdawson@gmail.com>
Message-ID: <20120731041236.GB15166@thyrsus.com>
References: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] ARM/uClibc build problem
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 04:12:40 -0000

Simon Dawson <spdawson@gmail.com>:
> Using Buildroot, I'm cross compiling gpsd 3.7 for ARM, using uClibc.
> The build is falling over with the following error.
> 
>   gpsmon.o: In function `monitor_fixframe':
>   gpsmon.c:(.text+0x264): undefined reference to `acs_map'
>   monitor_nmea.o: In function `nmea_update':
>   monitor_nmea.c:(.text+0xbc0): undefined reference to `acs_map'
>   collect2: ld returned 1 exit status
>   scons: *** [gpsmon] Error 1
>   scons: building terminated because of errors.
> 
> I'm working around this by adding the following line to the gpsmon.c
> and monitor_nmea.c source files.
> 
>   unsigned long acs_map[128];
> 
> What I'm wondering is whether there might be a way of resolving this
> issue in a less ugly way --- preferably, directly in the gpsd build
> system. Does anybody have any suggestions?

Aha.  Your acs_map is a curses thing - I think the failure to link means
that your curses library conforms to the old BSD interface and is missing
System V features.  If you upgrade to something like ncurses all should
be well.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Tue Jul 31 00:21:47 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sw3xr-00025Z-Fn
	for mharc-gpsd-dev@gnu.org; Tue, 31 Jul 2012 00:21:47 -0400
Received: from eggs.gnu.org ([208.118.235.92]:60779)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3xp-000245-9P
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:21:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3xo-0007Bo-CT
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:21:45 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:47584 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw3xo-0007Bi-8N
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:21:44 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id EB2CD40556; Tue, 31 Jul 2012 00:21:42 -0400 (EDT)
Date: Tue, 31 Jul 2012 00:21:42 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: KIU Shueng Chuan <nixchuan@gmail.com>
Message-ID: <20120731042142.GC15166@thyrsus.com>
References: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] devtools/ais.py type25 parsing bug
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 04:21:46 -0000

KIU Shueng Chuan <nixchuan@gmail.com>:
> In devtools/ais.py from gpsd release 3.7, the bitfield definition of
> "type25" is causing a TypeError exception in aivdm_unpack().
>  
> Changing None to 0 in the bitfield definition makes it work.
>
> For reference, the following was the sentence that triggered it:
> !AIVDM,1,1,,B,I9NS<Lh01dWK:UN0bOM2MR2d0<<K,0*58

Fix merged, thanks.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Tue Jul 31 00:25:35 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sw41X-0002S2-TU
	for mharc-gpsd-dev@gnu.org; Tue, 31 Jul 2012 00:25:35 -0400
Received: from eggs.gnu.org ([208.118.235.92]:40604)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw41V-0002PD-1J
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:25:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw41T-0008FP-O9
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:25:32 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net
	([71.162.243.5]:47588 helo=snark.thyrsus.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <esr@thyrsus.com>) id 1Sw41T-0008FL-KA
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 00:25:31 -0400
Received: by snark.thyrsus.com (Postfix, from userid 1000)
	id 998DE40556; Tue, 31 Jul 2012 00:25:30 -0400 (EDT)
Date: Tue, 31 Jul 2012 00:25:30 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Christian Gagneraud <chris@techworks.ie>
Message-ID: <20120731042530.GD15166@thyrsus.com>
References: <CAP2skc-FYYQLZcvqZPk4k3+U2WVdEvCn_1gwcs2u7zUENtW6KA@mail.gmail.com>
	<5012AA1D.8010802@techworks.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5012AA1D.8010802@techworks.ie>
Organization: Eric Conspiracy Secret Labs
X-Eric-Conspiracy: There is no conspiracy
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 71.162.243.5
Cc: gpsd-dev@nongnu.org
Subject: Re: [gpsd-dev] devtools/ais.py type25 parsing bug
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: esr@thyrsus.com
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 04:25:34 -0000

Christian Gagneraud <chris@techworks.ie>:
> Thanks for pointing that out. I will fix that shortly.

I got it.

Chris, while investigating this I noted that you added some
type 25 and 26 test sentences to sampole.aivdm.  That's good,. but please
add comments giving the ASCII field decode as with the other message types.

That file is intended to document the correct decodings for its test 
sentences so they can be re-examined whenever something perturbs the 
check file.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


From MAILER-DAEMON Tue Jul 31 03:41:49 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sw75Q-0003tZ-Vk
	for mharc-gpsd-dev@gnu.org; Tue, 31 Jul 2012 03:41:48 -0400
Received: from eggs.gnu.org ([208.118.235.92]:54635)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1Sw75L-0003so-9N
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 03:41:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1Sw75H-0004Nr-FV
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 03:41:43 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:62509)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <spdawson@gmail.com>) id 1Sw75H-0004Nl-9B
	for gpsd-dev@nongnu.org; Tue, 31 Jul 2012 03:41:39 -0400
Received: by pbbro12 with SMTP id ro12so10703893pbb.4
	for <gpsd-dev@nongnu.org>; Tue, 31 Jul 2012 00:41:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=1FIXjFvfv/gkoBSHZl6c4e7kv2NarxzSvqx5Lnqi/ZA=;
	b=mfFI4FIlfrqFafgFIJTn1KdWpBBja00H38TJqRNhadw1msgpwHnDhsTre9nLJdMMz/
	05x34sRY1lAqqdQ0352X07z++pU5sijHeAkhP5A7/tB094f5FMPSgnw4ALdzVHpePr9D
	MXll2Ps4De5ZWL4Umcl7rgYV5KgxG+itlDKMT7LPTAnj07OAtw3MkeBUC6k3KQgS+zHq
	v1gBiV3dQEHxls4RRtGi9G+7gwhlQPUm1v5flGQXXN13ChIB/RcLF9NJhZvwxfXc33L4
	uaEZEMAL1JGwDmRN/I0oQ1s+0grzNu8dnSG/I6uV3fuF3e1OL5V27w9q5fEV+VxXT/RP
	gZ7Q==
MIME-Version: 1.0
Received: by 10.68.236.67 with SMTP id us3mr41263823pbc.80.1343720497990; Tue,
	31 Jul 2012 00:41:37 -0700 (PDT)
Received: by 10.68.60.227 with HTTP; Tue, 31 Jul 2012 00:41:37 -0700 (PDT)
In-Reply-To: <20120731041236.GB15166@thyrsus.com>
References: <CAHt8ZCN8fzxZmjWen+UfN5pfe_kQLUBBJ+k2K1JKPyZhr+CuNA@mail.gmail.com>
	<20120731041236.GB15166@thyrsus.com>
Date: Tue, 31 Jul 2012 08:41:37 +0100
Message-ID: <CAHt8ZCMTuJW9V6eQO6-MSeGFOXGRu=VEzLCiZwZ569aEmmVuDw@mail.gmail.com>
From: Simon Dawson <spdawson@gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 209.85.160.45
Subject: Re: [gpsd-dev] ARM/uClibc build problem
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 07:41:47 -0000

Hi Bernd, Eric. Thanks for taking the time to reply to this.

On 31 July 2012 05:12, Eric S. Raymond <esr@thyrsus.com> wrote:
> Aha.  Your acs_map is a curses thing - I think the failure to link means
> that your curses library conforms to the old BSD interface and is missing
> System V features.  If you upgrade to something like ncurses all should
> be well.

It actually turned out to be a problem with how the version of ncurses
in Buildroot uses pkg-config in its configure script. In any case, my
problem is now solved.

Simon.


