Thanks, Richard, for such a detailed answer!
I'll try to find another solution to handle it.
On Sun, 26 Nov 2023 at 22:10, Richard Cochran
wrote:
> On Sun, Nov 26, 2023 at 01:38:15PM +0300, IlorDash wrote:
> > Could you, please, explain why you think my hardware is broken? I
Could you, please, explain why you think my hardware is broken? I thought,
since SYNC and DELAY_REQ filters are defined in Linux, ptp4l can use them
to set type-specific hardware filters.
On Sat, 25 Nov 2023 at 22:22, Richard Cochran
wrote:
> On Fri, Nov 24, 2023 at 10:29:12PM +0300, IlorD
From: Ilya Orazov
I’m using an Ethernet controller with PTP support, which requires
determining which PTP packets on RX must be timestamped: SYNC or
DELAY_REQ, based on whether the device is Slave or Master respectively.
So I can’t use the EVENT RX filter and must dynamically switch RX
filters,
n the description.
On Tue, 14 Nov 2023 at 23:21, Erez wrote:
>
>
> On Tue, 14 Nov 2023 at 23:21, Erez wrote:
>
>
> On Mon, 13 Nov 2023 at 18:49, IlorDash wrote:
>
>> From: Ilya Orazov
>>
>> Added adv_rx_filter config that allows to send SIOCSHWTSTAMP i
at 15:29, Miroslav Lichvar wrote:
> On Mon, Nov 13, 2023 at 08:47:48PM +0300, IlorDash wrote:
> > I assumed, if these filters are defined in Kernel, they might be used in
> > ptp4l utility to fix this. So I added adv_rx_filter config that allows
> > to sen
From: Ilya Orazov
Added adv_rx_filter config that allows to send SIOCSHWTSTAMP ioctl with
HWTSTAMP_FILTER_PTP_XXX_SYNC or HWTSTAMP_FILTER_PTP_XXX_DELAY_REQ
rx filters based on whether the Device is Slave or Master respectively.
This Feature is added for all transport levels.
I’m using Ethernet
