Re: [Linuxptp-devel] unknown option ntpshm_segment at line 8 in eno1 section

2015-08-04 Thread Miroslav Lichvar
On Tue, Aug 04, 2015 at 08:43:11PM +, Gary E. Miller wrote: > cat ${CONF1} > [global] > uds_address /var/run/ptp4l > #network_transport L2 > network_transport UDPv6 > > clock_servo ntpshm > ntpshm_segment 0 > cat ${CONF2} > [global] >

Re: [Linuxptp-devel] unknown option ntpshm_segment at line 8 in eno1 section

2015-08-04 Thread Gary E. Miller
Yo Miroslav! On Tue, 4 Aug 2015 10:34:17 +0200 Miroslav Lichvar wrote: > > Interesting, can you share your setup? > > When I run "ptp4l -6 -S -i ens5 -m", ss reports only IPv6 sockets for > ptp4l: For comparison, here is what I get when trying both UPDv4 and UDPv6: export CONF1=ptp-backu

Re: [Linuxptp-devel] unknown option ntpshm_segment at line 8 in eno1 section

2015-08-04 Thread Gary E. Miller
Yo Miroslav! On Tue, 4 Aug 2015 10:34:17 +0200 Miroslav Lichvar wrote: > > Interesting, can you share your setup? > When I run "ptp4l -6 -S -i ens5 -m", ss reports only IPv6 sockets for > ptp4l: > > # ss -lup | grep ptp4l > UNCONN 0 > 0 ::%ens5:ptp-event :::

Re: [Linuxptp-devel] unknown option ntpshm_segment at line 8 in eno1 section

2015-08-04 Thread Miroslav Lichvar
On Mon, Aug 03, 2015 at 08:58:20PM +, Gary E. Miller wrote: > > You can even run multiple ptp4l instances in different PTP domains on > > the same NIC (only one using HW timestamping). > > Assuming I could get HW timestamping to work. Trying on many hosts > with a few deffferent NIC types the

Re: [Linuxptp-devel] [PATCH] Add options to configure TTL/hop limit for UDP/UDP6 transports.

2015-08-04 Thread Miroslav Lichvar
On Mon, Aug 03, 2015 at 10:02:06PM +0200, Richard Cochran wrote: > On Mon, Aug 03, 2015 at 03:49:43PM +0200, Miroslav Lichvar wrote: > > +unsigned char udp_ttl = 1; > ... > This would be better it it were a per-port option, no? Definitely. That's actually how I originally wanted it, but when I saw

Re: [Linuxptp-devel] discrepancy between ptp4l output and oscilloscope readings on Beaglebone Black

2015-08-04 Thread Juan Solano
thanks for your suggestion, Kim. What kind of values are you getting? Juan. On Wed, Jul 29, 2015, at 07:41 PM, Yursen Kim wrote: > We implemented PPS output signal through AM335x Dual-Mode Timer > running in the PWM mode with SCLK frequency. > > This is more accurate than software GPIO output bec

Re: [Linuxptp-devel] discrepancy between ptp4l output and oscilloscope readings on Beaglebone Black

2015-08-04 Thread Juan Solano
Richard, thanks for your suggestion. I was using PREEMPT initially, and with PREEMPT RT I see some improvements, clocks are synchronized in the +- 250ns range. Regards, Juan. On Wed, Jul 29, 2015, at 06:17 PM, Richard Cochran wrote: > On Wed, Jul 29, 2015 at 05:28:12PM +0200, Juan Solano wrote: >