. ITU-T). And for those profiles that use L1Sync (i.e. HA
Profile), by all means, this belongs in linuxptp project as it's part of PTP
(and in this case, the L1Sync interface is likely going through PHC) - but
please don't confuse this with ITU-T's SyncE as they are not related.
Re
Hi Michał,
Please see my responses inline.
Regards,
Greg
-Original Message-
From: Michalik, Michal
Sent: Friday, July 29, 2022 12:25 PM
To: Greg Armstrong ; richardcoch...@gmail.com
Cc: linuxptp-devel@lists.sourceforge.net; Kubalewski, Arkadiusz
; Miroslav Lichvar ; Erez
Subject
Hi Richard,
Virtual PTP Port is defined in Annex B of G.8275. It was moved to
recommendation G.8275 since it can be used in both G.8275.1 and G.8275.2
Profiles. It was defined before 1588-2019 Special Port. There are similarities,
but not the same.
APTS stands for Assisted Partial Time Support
project
with other MAC/PHY/SoC vendors looking for an ESMC protocol solution.
Regards,
Greg
Greg Armstrong
Principal System Architect, Timing Products Division
Renesas Electronics Canada Limited
Mobile: 1-613-218-9373
-Original Message-
From: Miroslav Lichvar
Sent: Thursday, June 2,
I'm only
aware of the HA profile using it right now.
Greg
-Original Message-
From: Miroslav Lichvar
Sent: June 1, 2022 11:19 AM
To: Greg Armstrong
Cc: Richard Cochran ; piotr.kwapulin...@intel.com;
anatolii.gerasyme...@intel.com; andrzej.saw...@intel.com;
linuxptp-devel@lists.sou
022 10:44 AM
To: Greg Armstrong ; Miroslav Lichvar
Cc: Kwapulinski, Piotr ; Sawula, Andrzej
; linuxptp-devel@lists.sourceforge.net; Gerasymenko,
Anatolii
Subject: RE: [Linuxptp-devel] [PATCH 00/11] synce4l: add software for
Synchronous Ethernet
-Original Message-----
From: Greg Armstrong
TU-T
recommendations that synce4l must follow).
Greg
Greg Armstrong
Principal System Architect, Timing Products Division
Renesas Electronics Canada Limited
Mobile: 1-613-218-9373
-Original Message-
From: Miroslav Lichvar
Sent: June 1, 2022 3:33 AM
To: Greg Armstrong
Cc: Richard Cochran ; p
stract the
hardware for user space programs, I would suspect a similar SyncE Hardware
Clock infrastructure will be needed in Linux to allow for abstraction of
hardware used by synce4l (i.e. as this project matures to meet the full
recommendations in G.8264 and, as required, G.781).
Greg
Greg
ter” should remain “Grandmaster”.
Use of other terms (i.e. client) should be avoided to prevent disconnect from
the IEEE standard.
Greg
Greg Armstrong
Principal System Architect, Timing Products Division
Renesas Electronics Canada Limited
Mobile: 1-613-218-9373
From: Erez
Sent: May 16, 2022
The latest 802.1AS has clarified ptpTimescale flag is only used for Announce.
For all other messages, it should be FALSE (and still ignored on reception).
Thus, the patch should not be the default. I agree with Jacob that a use of a
flag may be better to allow interop with other gPTP implementat
ter FAULTY state. This would explain what was observed of
toggling in/out of FAULTY state.
Greg
-Original Message-
From: Miroslav Lichvar
Sent: May 10, 2021 7:58 AM
To: Greg Armstrong
Cc: Amar Subramanyam ;
linuxptp-devel@lists.sourceforge.net
Subject: Re: [Linuxptp-devel] [PATCH] S
be 255 as specified in 7.6.2.5.
>From IEEE1588-2019 Table 4:
255 | Shall be the clockClass of a slave-only PTP Instance
(see 9.2.2.1).
And clause 9.2.2.1 title is "Slave-Only Ordinary Clocks".
Greg
-Original Message-
From: Greg Armstrong
Sent: May 7,
One possible issue is you are setting clientOnly=1 for a BC; this is not
allowed per IEEE1588 (as a BC shall not be a slaveOnly PTP Instance).
>From IEEE1588-2019:
9.2.3 Non-slaveOnly PTP Instances
A Boundary Clock shall not be a slaveOnly PTP Instance. Ordinary Clocks
not desig
13 matches
Mail list logo
