Hello,
Any idea when is the next planned release for ptp4l?
We are currently using 3.1.1 release, but we need fixes present in the current
base code.
Is it ok to take these missing fixes and merge into 3.1.1 local code base?
For Example:
commit e8dc364f9fd5fbdac5d2c5e433f28e9da0028d49
*It seems the first clock step is disabled. Did you
changefirst_step_threshold in your config?*
It is set to the default value itself(0.2).
On Mon, Jan 23, 2023 at 4:31 PM Miroslav Lichvar
wrote:
> On Mon, Jan 23, 2023 at 03:54:27PM +0530, Aditya Venu wrote:
> > *Does it work if you enable
On Mon, Jan 23, 2023 at 04:36:11PM +0530, Aditya Venu wrote:
> *It seems the first clock step is disabled. Did you
> changefirst_step_threshold in your config?*
>
> It is set to the default value itself(0.2).
I have no explanation. Sorry.
--
Miroslav Lichvar
_
On Mon, Jan 23, 2023 at 03:54:27PM +0530, Aditya Venu wrote:
> *Does it work if you enable SW timestamping on the client?*
>
> I'm pasting the output below with HW timestamping at master and SW
> timestamping on client:
It seems the first clock step is disabled. Did you change
first_step_threshol
*Does it work if you enable SW timestamping on the client?*
I'm pasting the output below with HW timestamping at master and SW
timestamping on client:
*ptp4l[641.740]: port 1: INITIALIZING to LISTENING on
INIT_COMPLETEptp4l[641.740]: port 0: INITIALIZING to LISTENING on
INI
On Mon, Jan 23, 2023 at 11:54:25AM +0530, Aditya Venu wrote:
> Any suggestions to the above issue please?!
I don't see anything wrong in the phc2ctl output, but your ptp4l
output shows frequency stuck at -1, which makes no sense to me.
Does it work if you enable SW timestamping on client?
What NIC
