On Wednesday, November 28, 2012 6:54:17 AM UTC+8, unruh wrote:
>
> What kind of platform is that?
>
TP-LINK TL-WR841N (Atheros ar71xx), see
http://code.google.com/p/openwrt-stratum1
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.
On 2012-11-27, David Taylor wrote:
> On 27/11/2012 15:13, unruh wrote:
>> On 2012-11-27, David Taylor wrote:
>>> Ralph, thanks for your pointer about rebuilding the kernel. Not
>>> trivial, is it!
>>>
>>> BTW: this post seems to have fallen off my NNTP client but I had already
>>
>> It should be
On 2012-11-27, gabs wrote:
> On Sunday, November 25, 2012 3:56:28 AM UTC+8, David Taylor wrote:
>> I've just started the statistics collection on my Linux/RPi NTP server,
>> and when plotting the jitter results I found that most of the values
>> were zero. I don't see that on my Windows stratum
On 27/11/2012 15:13, unruh wrote:
On 2012-11-27, David Taylor wrote:
Ralph, thanks for your pointer about rebuilding the kernel. Not
trivial, is it!
BTW: this post seems to have fallen off my NNTP client but I had already
It should be possible to compile the gpio interrupt driver as a modul
On 27/11/2012 16:24, gabs wrote:
[]
The displayed jitter in loopstats or the peer list can be different from the
actual jitter of the source. This case is the reverse: low actual jitter,
15 us displayed jitter.
root@OpenWrt:/tmp# tail /tmp/ntp/loops
56257 76888.554 -0.00080 6.553 0.15259
On Sunday, November 25, 2012 3:56:28 AM UTC+8, David Taylor wrote:
> I've just started the statistics collection on my Linux/RPi NTP server,
> and when plotting the jitter results I found that most of the values
> were zero. I don't see that on my Windows stratum-1 systems. Is there
> a limit
On 2012-11-27, David Taylor wrote:
> Ralph, thanks for your pointer about rebuilding the kernel. Not
> trivial, is it!
>
> BTW: this post seems to have fallen off my NNTP client but I had already
It should be possible to compile the gpio interrupt driver as a module,
and just compile it, not t
Ralph, thanks for your pointer about rebuilding the kernel. Not
trivial, is it!
BTW: this post seems to have fallen off my NNTP client but I had already
copied it. It also seems to have posted the same message twice, of at
least an earlier, uncorrected version, sigh!
--
Cheers,
David
Web: h
On 26/11/2012 23:59, David Woolley wrote:
David Taylor wrote:
server reached over the LAN to have an offset of -0.028 milliseconds,
whereas its own PPS source is reported to have an offset of -0.001
milliseconds. Is that the right sign and amount for the offsets you
might expect comparing the
On 26/11/2012 23:59, David Woolley wrote:
Offsets should be randomly distributed between + and - signs. If they
are all of one sign, you are not locked up or there is a bug. They
should be of s similar magnitude to the jitter.
They may not be evenly distributed, because of limitations of the
n
David Taylor wrote:
> BTW: I would like to get step-by-step instructions for recompiling the
> kernel with the gpio-pps added, as I'm using someone else's kernel and I
> may need to make my own when upgrading in the future.
I did it with
http://elinux.org/RPi_Kernel_Compilation
After zcat /pr
On 26/11/2012 21:27, Dave Morgan wrote:
[]
My Pi ntp server ... syncing to other ntp pool servers only
(not stratum 1 yet)
56257 943.692 0.000152844 -4.041 0.000616901 0.028755 10
56257 2672.693 0.000354418 -4.038 0.000581443 0.026910 10
56257 3558.700 -0.000495198 -4.040 0.000621327 0.025178 10
On 27/11/2012 07:05, james machado wrote:
[]
on my RPi running as at stratum 1
[]
i checked my loopstats for the last 47,000 odd lines of loopstats I
have had 7 lines where the jitter has not been zero.
james
Thanks, James! Good to know I am not alone!
BTW: I would like to get step-by-step
13 matches
Mail list logo
