From: Peter Seiderer <ps.report@gmx.net>
To: Guillaume Bres <guillaume.bressaix@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [v3] package/ntpsec: new package
Date: Thu, 24 Feb 2022 23:07:44 +0100 [thread overview]
Message-ID: <20220224230744.1306f790@gmx.net> (raw)
In-Reply-To: <CAJe0E3fs9xSP3jEQ__1_6JWRLYTMMywouQdF6kVKCu=4ykf2Bg@mail.gmail.com>
Hello Guillaume,
On Wed, 23 Feb 2022 18:51:59 +0100, Guillaume Bres <guillaume.bressaix@gmail.com> wrote:
> Hello Peter,
>
> sorry for the delayed test, the usual "busy on too many things".
>
> Today I ran the current patch serie on "zedboard_defconfig": everything
> works fine but SYNC is never fully acquired. The estimated "offsets" from
> the pool is close to 2^32 (limit?), jitter is large, delay is realistic,
> but those values never get averaged out.
Do you mean 'zynq_zed_defconfig' or do you work on an legacy buildroot version?
Can spot nothing special in the defconfig despite an ancient linux kernel/headers
version (4.16, or 3.18 in legacy zedboard_defconfig)...
Anything special in the config file?
> What do you think is going on? I don't think it's related to our work but
> to the demon itself.
Maybe better ask at ntpsec mailing list/bugtracker ([1])?
> v1_2_1 is fairly old, I hope they provide a new tag soon because a lot of a
> work has been accomplished in the meantime.
New release seems to be scheduled for end of this month [2]...
>
> At work we use our custom fork (for custom encryption), I rebased to master
> last week, I have never experienced such behavior.
Did only test/run on raspberry pi 3/4 (both 32 and 64 bit, glibc, uclibc)...
Regards,
Peter
[1] https://www.ntpsec.org/channels.html
[2] https://lists.ntpsec.org/pipermail/devel/2022-February/009961.html
>
> Guillaume W. Bres
> Software engineer
> <guillaume.bressaix@gmail.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-02-24 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 17:51 [Buildroot] [v3] package/ntpsec: new package Guillaume Bres
2022-02-24 22:07 ` Peter Seiderer [this message]
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=20220224230744.1306f790@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
--cc=guillaume.bressaix@gmail.com \
/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