From: Fabian Pflug <f.pflug@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Fabian Pflug <f.pflug@pengutronix.de>
Subject: [ptxdist] [PATCH] ntp: make sntp configureable
Date: Thu, 14 Aug 2025 11:54:52 +0200 [thread overview]
Message-ID: <20250814095452.1950806-1-f.pflug@pengutronix.de> (raw)
Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
---
rules/ntp.in | 12 +++++++++++-
rules/ntp.make | 10 +++++++++-
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/rules/ntp.in b/rules/ntp.in
index 2d85c8fac..0d80840c2 100644
--- a/rules/ntp.in
+++ b/rules/ntp.in
@@ -97,6 +97,17 @@ config NTP_CRYPTO
help
FIXME: This item needs to be documented
+config NTP_SNTP
+ bool
+ prompt "build SNTP"
+ help
+ Simple Network Time Protocol is a subset of the Network
+ Time Protocol (NTP). SNTP can be used when the ultimate
+ performance of a full NTP implementation based on
+ RFC 1305 is neither needed nor justified.
+ It is strongly recommended that SNTP be used only at
+ the extremities of the synchronization subnet.
+
comment "Clock drivers"
config NTP_ALL_CLOCK_DRIVERS
@@ -176,4 +187,3 @@ endif
comment "NTP conflicts with OpenNTPD"
depends on NTP && OPENNTPD
-
diff --git a/rules/ntp.make b/rules/ntp.make
index 9c6c9555d..429023645 100644
--- a/rules/ntp.make
+++ b/rules/ntp.make
@@ -128,7 +128,7 @@ NTP_CONF_OPT := \
--disable-kmem \
--enable-accurate-adjtime \
--disable-simulator \
- --without-sntp \
+ --$(call ptx/wwo, PTXCONF_NTP_SNTP)-sntp \
--without-ntpsnmpd \
--$(call ptx/endis, PTXCONF_NTP_SLEW_ALWAYS)-slew-always \
--$(call ptx/endis, PTXCONF_NTP_STEP_SLEW)-step-slew \
@@ -180,6 +180,14 @@ ifdef PTXCONF_NTP_NTPD
@$(call install_alternative, ntp, 0, 0, 0644, /etc/ntp-server.conf)
endif
+# #
+# # sntp client
+# #
+ifdef PTXCONF_NTP_SNTP
+ @$(call install_copy, ntp, 0, 0, 0755, -, \
+ /usr/sbin/sntp)
+endif
+
ifdef PTXCONF_NTP_NTPD_STARTSCRIPT
@$(call install_alternative, ntp, 0, 0, 0755, /etc/init.d/ntp-server)
--
2.39.5
reply other threads:[~2025-08-14 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250814095452.1950806-1-f.pflug@pengutronix.de \
--to=f.pflug@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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