Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subordinate/Slave just a bunch of devices(jbod) feature.

See my response inline: Thanks, Ramana -Original Message- From: Miroslav Lichvar [mailto:mlich...@redhat.com] Sent: 27 April 2021 20:59 To: Ramana Reddy Cc: linuxptp-devel@lists.sourceforge.net; Amar Subramanyam Subject: Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subordinat

Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subordinate/Slave just a bunch of devices(jbod) feature.

-Original Message- From: Miroslav Lichvar [mailto:mlich...@redhat.com] Sent: 27 April 2021 21:54 To: Ramana Reddy Cc: linuxptp-devel@lists.sourceforge.net; Amar Subramanyam; Richard Cochran (richardcoch...@gmail.com) Subject: Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subo

Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subordinate/Slave just a bunch of devices(jbod) feature.

-Original Message- From: Richard Cochran [mailto:richardcoch...@gmail.com] Sent: 27 April 2021 21:47 To: Ramana Reddy Cc: Miroslav Lichvar; linuxptp-devel@lists.sourceforge.net; Amar Subramanyam Subject: Re: [Linuxptp-devel] [PATCH] To support Ordinary Clock-Subordinate/Slave just a bun

Re: [Linuxptp-devel] [PATCH] Sync issues observed when ptp4l is ran with jbod and client only mode (clientOnly=1 and boundary_clock_jbod=1)

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