On Thu, Jun 04, 2020 at 12:09:48AM +1000, Luke Howard via Linuxptp-devel wrote: > > I don't know much about the audio profiles. Are they using a different > > transport or domain? A better way to do this might be to run two > > ptp4l instances on the interface. > > > Oddly that actually didn’t occur to me. Yes, AES67 is using PTPv2 over UDP, > and AVB is using 802.12AS (L2). It does seem more elegant for there to be a > single clock domain across the two profiles. But I’ll definitely try approach > and see if it is more stable.
If you do use 2x ptp4l on one interface, be sure only one ptp4l can adjust the clock! I recommend using two network ports. You really shouldn't mix the two protocols on the same network. Also, if you use two ports with one ptp4l, you can bridge the two protocols in a way that lets the bridge ports change rolls. IOW, you can synchronize your gPTP clients to your 1588 time server, or vise versa. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
