From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 4/5] gpsd: add optional support for KPPS interface
Date: Thu, 28 Aug 2014 16:29:50 +0200 [thread overview]
Message-ID: <20140828142950.GE16066@jama> (raw)
In-Reply-To: <1409227581-20888-5-git-send-email-pab@pabigot.com>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
On Thu, Aug 28, 2014 at 07:06:20AM -0500, Peter A. Bigot wrote:
> gpsd by default builds with PPS (pulse-per-second) support, but without
> kernel support to capture the edge of the pulse the accuracy is only
> +/-5us. Under Linux the pps-tools package installs the header required
> for the user-level API to the RFC 2783 KPPS interface. If gpsd detects
> this header, it will use the API to improve accuracy to +/-1us.
>
> See: http://www.catb.org/gpsd/gpsd-time-service-howto.html#_enabling_pps
>
> Signed-off-by: Peter A. Bigot <pab@pabigot.com>
> ---
> meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb b/meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb
> index d12c7a8..1c2d9eb 100644
> --- a/meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb
> +++ b/meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb
> @@ -20,6 +20,9 @@ SRC_URI = "${SAVANNAH_GNU_MIRROR}/${BPN}/${BP}.tar.gz \
> SRC_URI[md5sum] = "fc5b03aae38b9b5b6880b31924d0ace3"
> SRC_URI[sha256sum] = "706fc2c1cf3dfbf87c941f543381bccc9c4dc9f8240eec407dcbf2f70b854320"
>
> +PACKAGECONFIG ??= ""
> +PACKAGECONFIG[kpps] = ",,pps-tools"
Both recipes need some way of explicit disable of pps-tools, so that the
result is the same when building gpsd or ntp before or after pps-tools.
> inherit scons update-rc.d python-dir pythonnative systemd
>
> INITSCRIPT_NAME = "gpsd"
> --
> 1.8.5.5
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-28 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 12:06 [meta-oe][PATCH 0/5] ntpd and gpsd updates for high-precision timing Peter A. Bigot
2014-08-28 12:06 ` [meta-oe][PATCH 1/5] ntp: re-enable server debugging and control by PACKAGECONFIG Peter A. Bigot
2014-08-28 12:06 ` [meta-oe][PATCH 2/5] gpsd: update to 3.10 Peter A. Bigot
2014-08-28 12:06 ` [meta-oe][PATCH 3/5] pps-tools: add recipe Peter A. Bigot
2014-08-28 12:06 ` [meta-oe][PATCH 4/5] gpsd: add optional support for KPPS interface Peter A. Bigot
2014-08-28 12:53 ` Burton, Ross
2014-08-28 13:05 ` Peter A. Bigot
2014-08-28 14:32 ` Martin Jansa
2014-08-28 15:23 ` Peter A. Bigot
2014-08-28 15:47 ` Martin Jansa
2014-08-28 15:51 ` Peter A. Bigot
2014-08-28 15:48 ` Peter A. Bigot
2014-08-28 16:25 ` Martin Jansa
2014-08-28 14:29 ` Martin Jansa [this message]
2014-08-28 17:42 ` [meta-oe][PATCH v2] gpsd: add deterministic " Peter A. Bigot
2014-08-28 12:06 ` [meta-oe][PATCH 5/5] ntp: add optional " Peter A. Bigot
2014-08-28 17:43 ` [meta-networking][PATCH v2] ntp: add deterministic " Peter A. Bigot
2014-09-29 7:50 ` Rongqing Li
2014-09-29 10:19 ` Peter A. Bigot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140828142950.GE16066@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox