You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement the 'Path trace' optional feature of IEEE1588-2019 section 16.2. This feature has two parts, sending and receiving. Either could be implemented independently but it would be desirable to present the two parts together to aid testability and review.
Option to append PATH_TRACE TLV to outgoing Announce messages
Implement the 'Path trace' optional feature of IEEE1588-2019 section 16.2 by appending PATH_TRACE TLVs to outgoing Announce messages, controlled via an instance-scope configuration option to the PTP sync module.
The PORT_COMMUNICATION_AVAILABILITY TLV provides an example of how to add an optional TLV to outgoing announce messages:
- these are the foreign master records. It is a trade off between space for storing for all foreign masters and accessing later via FMR for selected master or a more complex solution. I suggest doing the former.
Expand the topology where the clock list for parent nodes is available:
Other than the configuration, this is the only part of the solution which is outside of the ptpd2 fork. The coding standard/convention is slightly different here. The native sfptpd and vendored ptpd2 parts of the application are broadly linked via the ptpd_lib.c and ptpd_lib.h files. The configuration and state objects are incorporated into the sfptpd_ptp_module.c instance state but preferably accessed via accessors in ptpd_lib.
The text was updated successfully, but these errors were encountered:
Implement the 'Path trace' optional feature of IEEE1588-2019 section 16.2. This feature has two parts, sending and receiving. Either could be implemented independently but it would be desirable to present the two parts together to aid testability and review.
Option to append
PATH_TRACE
TLV to outgoing Announce messagesImplement the 'Path trace' optional feature of IEEE1588-2019 section 16.2 by appending
PATH_TRACE
TLVs to outgoing Announce messages, controlled via an instance-scope configuration option to the PTP sync module.The
PORT_COMMUNICATION_AVAILABILITY
TLV provides an example of how to add an optional TLV to outgoing announce messages:sfptpd/src/ptp/ptpd2/constants.h
Line 335 in 3a4113b
sfptpd/src/ptp/ptpd2/dep/msg.c
Lines 2463 to 2493 in 3a4113b
sfptpd/src/ptp/ptpd2/protocol.c
Lines 3235 to 3241 in 3a4113b
Handle received
PATH_TRACE
TLVs for current parent.Example for port communication capabilities:
sfptpd/src/ptp/ptpd2/protocol.c
Lines 192 to 198 in 3a4113b
sfptpd/src/ptp/ptpd2/protocol.c
Lines 3184 to 3219 in 3a4113b
sfptpd/src/ptp/ptpd2/datatypes.h
Lines 83 to 84 in 3a4113b
sfptpd/src/ptp/sfptpd_ptp_module.c
Lines 2762 to 2789 in 3a4113b
ptpd2
fork. The coding standard/convention is slightly different here. The nativesfptpd
and vendoredptpd2
parts of the application are broadly linked via theptpd_lib.c
andptpd_lib.h
files. The configuration and state objects are incorporated into thesfptpd_ptp_module.c
instance state but preferably accessed via accessors inptpd_lib
.The text was updated successfully, but these errors were encountered: