On 1/5/2021 6:42 AM, Richard Cochran wrote:
> Signed-off-by: Richard Cochran <richardcoch...@gmail.com>
> ---
> phc2sys.8 | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
>
> diff --git a/phc2sys.8 b/phc2sys.8
> index b3a3de3..66007eb 100644
> --- a/phc2sys.8
> +++ b/phc2sys.8
> @@ -1,4 +1,4 @@
> -.TH PHC2SYS 8 "April 2018" "linuxptp"
> +.TH PHC2SYS 8 "January 2021" "linuxptp"
> .SH NAME
> phc2sys \- synchronize two or more clocks
>
> @@ -83,18 +83,10 @@ default.
> .TP
> .BI \-d " pps-device"
> Specify the PPS device of the master clock (e.g. /dev/pps0). With this option
> -the PPS synchronization mode is used instead of the direct mode. As the PPS
> -signal does not specify time and only marks start of a second, the slave
> clock
> -should be already close to the correct time before
> -.B phc2sys
> -is started or the
> -.B \-s
> -option should be used too. With the
> +the PPS synchronization mode is used instead of the direct mode. The
> +matching PHC must be specified using the
> .B \-s
Makes sense. We don't need a further explanation about the clocks being
close together because -s is always required now. ok.
> -option the PPS signal of the master clock is enabled automatically, otherwise
> -it has to be enabled before
> -.B phc2sys
> -is started (e.g. by running \f(CWecho 1 > /sys/class/ptp/ptp0/pps_enable\fP).
> +command line option.
> This option can be used only with the system clock as the slave clock. Not
> compatible with the
> .B \-a
>
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
