> -Original Message-
> From: Miroslav Lichvar
> Sent: Thursday, July 08, 2021 1:38 AM
> To: Keller, Jacob E
> Cc: Richard Cochran ; Дмитрий Кандыбка
> ; linuxptp-users@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] HW timestamp issue
>
> On Wed, Jul 0
On Wed, Jul 07, 2021 at 10:25:16PM +, Keller, Jacob E wrote:
> I would recommend trying a newer kernel and seeing if this improves. I am not
> really aware of any specific issue related to missing ingress timestamps
> though :(
The hardware has a PTP-specific RX filter. Is it not expected th
Le 08/07/2021 à 00:25, Keller, Jacob E a écrit :
>
>> -Original Message-
>> From: Richard Cochran
>> Sent: Wednesday, July 07, 2021 7:15 AM
>> To: Дмитрий Кандыбка
>> Cc: linuxptp-users@lists.sourceforge.net
>> Subject: Re: [Linuxptp-users] HW tim
> -Original Message-
> From: Richard Cochran
> Sent: Wednesday, July 07, 2021 7:15 AM
> To: Дмитрий Кандыбка
> Cc: linuxptp-users@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] HW timestamp issue
>
> On Wed, Jul 07, 2021 at 03:02:39PM +0300, Дмитрий Канд
On Wed, Jul 07, 2021 at 03:02:39PM +0300, Дмитрий Кандыбка wrote:
> I've met with ptp4l timesync issue. Master send SYNC packets without
> timestamp and slave doesn't handle this case when twoStepFlag set to 1. The
> IEEE 1588 standard says that SYNC messages in 2-step ptp don't need
> timestamp. I
Hello dear list!
I've met with ptp4l timesync issue. Master send SYNC packets without
timestamp and slave doesn't handle this case when twoStepFlag set to 1. The
IEEE 1588 standard says that SYNC messages in 2-step ptp don't need
timestamp. It enough to have timestamp in FOLLOW_UP messages. Such li
