> For starters, the two PPS pulses should be close enough together to trigger
> a back-to-back queued interrupt, so the second will have to wait for the
> first handler to complete.
You might learn something by connecting the same PPS signal to two pins and
comparing the time stamps. The diffe
Gary E. Miller via devel writes:
> Looking forward to your results. I suspect we'll be surprised by
> something in there.
For starters, the two PPS pulses should be close enough together to
trigger a back-to-back queued interrupt, so the second will have to wait
for the first handler to complete.
Yo Achim!
On Wed, 24 Jan 2018 21:48:48 +0100
Achim Gratz via devel wrote:
> Now I'll have to modify the NaviSys puck to get the hidden
> PPS out and connect it as a second PPS.
Looking forward to your results. I suspect we'll be surprised by something
in there.
RGDS
GARY
-
Gary E. Miller via devel writes:
> As of two mins ago, the improvement to allow multiple pps-gpio is
> now in git head.
Wonderful. I wish all that devicetree magic was better documented,
though… Now I'll have to modify the NaviSys puck to get the hidden PPS
out and connect it as a second PPS.
Yo Achim!
> > Bug filed with the Raspberry Pi kernel folks:
> > https://github.com/raspberrypi/linux/issues/2352
> I've asked that is be added to git head.
As of two mins ago, the improvement to allow multiple pps-gpio is
now in git head.
Many thanks to Phil Elwell for the fast work!
RGDS
Yo Achim!
> Bug filed with the Raspberry Pi kernel folks:
> https://github.com/raspberrypi/linux/issues/2352
Already an answer:
Take this overlay:
https://drive.google.com/file/d/1SRirIMwqLDgNHc3YTyUlB-rUuQtdtTym/view?usp=sharing
Apply to 4.9.19 or newer.
Add this to /boot/config.txt:
dtove
Yo All!
Sorry for the corss post. I mentioned this on the gpsd list and thought
some folks here might also be interested:
I just pushed clock_test.c to git head in contrib/. Basically, the
test runs two back to back clock_getttime(), then waits a bit for the
CPU cache to clear. The tests belo
Yo Achim!
On Wed, 24 Jan 2018 19:22:46 +0100
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > So, how about you file a bug with the RasPi kernel people?
>
> I think that should go straight to upstream kernel development.
> However I'm not sure if that subsystem is still in
Gary E. Miller via devel writes:
> So, how about you file a bug with the RasPi kernel people?
I think that should go straight to upstream kernel development. However
I'm not sure if that subsystem is still in active development, the
mailing list is more or less dormant. So, go ahead and try to f
Yo Achim!
On Wed, 24 Jan 2018 19:02:52 +0100
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > So the problem is with the RasPi kernel. Go ahead and nag them for
> > us.
>
> If you go back and actually read what I wrote at the beginning of the
> thread, it is a problem with
Frank Nicholas via devel writes:
> Unless the boards garner the same community/distro support as the
> Raspberry Pis, I don’t think they will go very far.
As long as the function I need for a headless box are supported in a
mainline kernel and they provide a halfway decent image to start from,
the
Gary E. Miller via devel writes:
> So the problem is with the RasPi kernel. Go ahead and nag them for us.
If you go back and actually read what I wrote at the beginning of the
thread, it is a problem with the gpio-pps driver. It only allows a
single GPIO to be configured for PPS. Both the seria
Accidentally replied to ESR directly instead of the list
Update on previous status.
On 01/09/2018 11:42 AM, Eric S. Raymond wrote:
Heads up, Hal! I'd like your opinopn on these.
Ian Bruene via devel:
* Time Resolution (not to be confused with Time /Precision/, which is one of
the first
13 matches
Mail list logo
