> > > Is it possible to force it to +0 like in the log of the
> > > first run above, the one that synchronizes?
>
> phc_ctl CLOCK_REALTIME freq 0
>
Hello, Miroslav, thank you very much.
BR.
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourcefo
On Tue, May 16, 2023 at 11:04:36AM -0300, Elder Costa wrote:
> > > ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1
> > > ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda
> > > ptp4l[488.262]: foreign master not using PTP timescale
> > > ptp4l[488.262]: port 1 (
> > ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1
> > ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda
> > ptp4l[488.262]: foreign master not using PTP timescale
> > ptp4l[488.262]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE
> > ptp4l[490.263]: ma
> ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1
> ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda
> ptp4l[488.262]: foreign master not using PTP timescale
> ptp4l[488.262]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE
> ptp4l[490.263]: master offse
Em qui., 11 de mai. de 2023 às 21:43, Richard Cochran <
richardcoch...@gmail.com> escreveu:
> Maybe you have ntpd or systemd timesync or chrony running on the
> client and/or the server?
>
> IIRC Ubuntu enables systemd thing by default, and it is hard to get
> rid of.
I disabled clock sync by NTP
On Thu, May 11, 2023 at 01:01:54PM -0300, Elder Costa wrote:
> The master offset increases, non monotonically but with a very definite
> trend, whether with or without the step_threshold parameter.
> What am I missing?
Maybe you have ntpd or systemd timesync or chrony running on the
client and/o
OK. Now the whale setup is properly working after I set one host to use
hardware timstamping and another one to use software timstamping. But ptp4l
will stuck on above mentioned state if both hosts are set to use software
timestamp. I am wondering why is that the case?
On Sun, Jan 17, 2021 at 12:5
Thank you for the replies,
On Fri, 24 Mar 2017 12:17:23 -0700
"Gary E. Miller" wrote:
> On Fri, 24 Mar 2017 20:09:29 +0100
> Richard Cochran wrote:
> > Wireless PTP is not going to work very well. I recommend using NTP
> > instead.
>
> Let us not make this a PTP vs. NTP thing. There is ong
Yo Richard!
On Fri, 24 Mar 2017 20:09:29 +0100
Richard Cochran wrote:
> On Fri, Mar 24, 2017 at 06:44:30PM +0100, Šimon Wernisch wrote:
> > Hello,
> > I am trying to use ptp4l with software timestamping on my raspberry
> > pi with a RT5370 wireless adapter. The driver is rt2800usb found in
> > d
On Fri, Mar 24, 2017 at 06:44:30PM +0100, Šimon Wernisch wrote:
> Hello,
> I am trying to use ptp4l with software timestamping on my raspberry pi
> with a RT5370 wireless adapter. The driver is rt2800usb found in
> drivers/net/wireless/ralink/rt2x00 of the raspberry kernel and it
> doesn't support
Hello,
I could make ptp4l working on Raspberry Pi, then I'd like to write about it.
- Raspberry Pi 3 Model B
- write image of Raspbian Jessie with Pixel to microSD
- installed linuxPTP v1.8
- installed ethtool
*** Rebuilding kernel configuration ***
(1) Make directory of kernel
$ cd
$ mkdi
On Sun, Nov 06, 2016 at 07:30:48PM +0100, Jan Deinhard wrote:
> $ ethtool -T eth0
> Time stamping parameters for eth0:
> Capabilities:
> software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
> software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
You are missing:
software-transmit (S
12 matches
Mail list logo
