Re: [Linuxptp-devel] SyncE support

2021-03-15 Thread Frantisek Rysanek
Dear gentlemen, thanks for opening this interesting topic... Is there any stock NIC (silicon, board), with an open-source Linux driver, that would support SyncE off the shelf in the NIC hardware? Other than that... SyncE sounds like a pretty self-contained L1 feature, at least considering just

Re: [Linuxptp-devel] SyncE support

2021-03-15 Thread Keller, Jacob E
> -Original Message- > From: Miroslav Lichvar > Sent: Monday, March 15, 2021 9:57 AM > To: linuxptp-devel@lists.sourceforge.net > Subject: [Linuxptp-devel] SyncE support > > As I understand it, there is currently no explicit support for SyncE > in the mainline kernel and linuxptp. For

[Linuxptp-devel] SyncE support

2021-03-15 Thread Miroslav Lichvar
As I understand it, there is currently no explicit support for SyncE in the mainline kernel and linuxptp. For example, there is no access to the Synchronization Status Message (SSM), so ptp4l cannot know if SyncE is active on a port. IIRC some people use SyncE with linuxptp by disabling the freque

[Linuxptp-devel] [PATCH 0/1] Ensure TLV_PORT_STATS_NP statistics uses little endian

2021-03-15 Thread Erez Geva
* Thirs round We use TLV_PORT_STATS_NP localy and over network. To prevent mismatch when the pmc and the ptp4l runs on mechine using different byte order. We change the statistics to little endian. We choose little endian since most of us use machines with little endian and we want to be backwar

[Linuxptp-devel] [PATCH 1/1] Ensure TLV_PORT_STATS_NP statistics uses little endian.

2021-03-15 Thread Erez Geva
As machine byte order may vary. Ensure TLV_PORT_STATS_NP statistics use defined order. As most of us use little endian hardware and to retain backward compatible with most of us, we decide to use little endian for the statistics. All other TLVs messages remain in network order. Signed-off-by: E

Re: [Linuxptp-devel] Unable to have UNCALIBRAT to SLAVE transition

2021-03-15 Thread Luigi 'Comio' Mantellini
continuing: In your opinion, can a servo->curr_offset_values = servo->num_offset_values call inside clock_udpdate_slave() help? ciao luigi Il giorno lun 15 mar 2021 alle ore 12:38 Luigi 'Comio' Mantellini ha scritto: > > Hi Richard, > > sorry again to continue this thread. > > Inside port_syn

Re: [Linuxptp-devel] Unable to have UNCALIBRAT to SLAVE transition

2021-03-15 Thread Luigi 'Comio' Mantellini
Hi Richard, sorry again to continue this thread. Inside port_synchronize() I noticed this: case SERVO_LOCKED: port_dispatch(p, EV_MASTER_CLOCK_SELECTED, 0); break; case SERVO_LOCKED_STABLE: message_interval_request(p, last_state, sync_interval); break; Supposing to have the port

[Linuxptp-devel] [PATCH] pmc: Fix printed totalCorrectionField.

2021-03-15 Thread Miroslav Lichvar
The value needs to be shifted to right to get nanoseconds. Signed-off-by: Miroslav Lichvar --- pmc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pmc.c b/pmc.c index 1e569b5..250124d 100644 --- a/pmc.c +++ b/pmc.c @@ -68,7 +68,7 @@ static void pmc_show_delay_timing(str