On Wed, Mar 15, 2023 at 01:14:50PM +0200, Kamil Zaripov wrote:
> The issue is ptp4l does not support out of the box creating two
> ports on the same network interfaces with different
> network_transport configuration values. I want to discuss how
> linuxptp code can be patched so user can do such
On 15/03/2023 13:51, Miroslav Lichvar wrote:
> On Wed, Mar 15, 2023 at 12:55:56PM +0100, Maciek Machnikowski wrote:
>> The SHM is not cleared upon servo release when exiting the tool. This leaves
>> the last update in the shared memory region marked as valid. As a result, the
>> NTP daemon start
On Wed, Mar 15, 2023 at 12:55:56PM +0100, Maciek Machnikowski wrote:
> The SHM is not cleared upon servo release when exiting the tool. This leaves
> the last update in the shared memory region marked as valid. As a result, the
> NTP daemon starting later may consume stale data if the producer proc
The SHM is not cleared upon servo release when exiting the tool. This leaves
the last update in the shared memory region marked as valid. As a result, the
NTP daemon starting later may consume stale data if the producer process
exited.
To prevent such behavior - invalidate the SHM data when releas
I have a setup where a local network has host with both IEEE 802.3 & UDP PTP
slaves and linux host that should run as PTP master. I used to run two ptp4l
processes (one with -2 argument and another one with -4 argument) on the master
host, but my network card cannot simultaneously timestamp seve
When ptp4l was configured to use SW timestamping, but the interface
supported also HW timestamping, ptp4l detected a change of the PHC on
start, switched to it from the system clock, and tried to control the
PHC using SW timestamps.
Don't switch the PHC if the current PHC index is -1, which is exp
> On 15 Mar 2023, at 01:55, Vladimir Oltean wrote:
>
> What will happen if the bridge floods the frame to 2 bridge ports, and
> both supports hardware TX timestamping? How many TX timestamps will be
> collected by the kernel, and more importantly, which ones? How many of
> those will be delivere
Hi Miroslav,
I tested this patch and it looks good!
Basic redundancy works too:
line 25 - ens1f0 goes to LISTENING, line 29 - ens1f1 is selected
line 44 - ens1f0 goes to SLAVE, line 48 - ens1f0 is selected
Log:
5 sh-4.4# /usr/sbin/phc2sys -a -r -n 24 -u 8 -m -z
/var/run/ptp4l.0.socket -z /var/ru
