Dear Experts,
Is there a particular reason that linuxptp does not support some SET commands
in PTP management client?
Example:
pmc -u -d 24 ´GET LOG_SYNC_INTERVAL´ is implemented
pmc -u -d 24 ´SET LOG_SYNC_INTERVAL´ is not implemented
Is this limitation only in PMC, that the composition of the
Hi Richard,
There is a demand for changing PORT_DATA_SET and probably CLOCK_DESCRIPTION
while ptp4l is running.
The main reason is due to the circumstances involved for stopping ptp4l,
modifying the config file (possibly from remote!), restarting ptp4l, and the
likelihood of config file corrupt
Hi Richard,
Thanks for clarification
There are some applications where a PTP clock node (i.e. a
master-only-ordinary-clock) will be configured from remote in a secure
environment, i.e. NETCONF YANG, or other transport technology (ITU PON, IEEE
PON, DOCSIS) specific management protocols. As you
Richard,
Another question:
What does the ´NP´ stand for, with management TLVs *_NP, such as
GRANDMASTER_SETTINGS_NP
PORT_DATA_SET_NP
TIME_STATUS_NP
Regards,
Albrecht
--
Announcing the Oxford Dictionaries API! The API off
This is a general question to the handling of ptp4l and phc2sys (-a -r) running
on PTP nodes:
Assuming PTP aware nodes (i.e. a 1588 capable switch acting as a BC, or an end
application acting as a PTP slave) are running ptp4l and probably phc2sys (-a
-r) for CLOCK_REALTIME synchronization.
Thes
Does the step threshold work on both ptp4l servo and phc2sys?
-Original Message-
From: Miroslav Lichvar [mailto:mlich...@redhat.com]
Sent: Tuesday, August 1, 2017 10:54 AM
To: Rommel, Albrecht
Cc: Linuxptp-devel@lists.sourceforge.net
Subject: Re: [Linuxptp-devel] PTP time re-arrangement
Hi all,
Ideally, the UDS port meets the requirements of a "virtual PTP port" as defined
in ITU-T G.8275.
A virtual PTP port supports all attributes as normally transported in Announce
messages or general PTP headers, except that the timing information comes via
technology proprietary methods, i
