On Wed, Nov 05, 2014 at 05:56:28PM +0100, Jiri Benc wrote: > My plan for the next steps has been allowing ptp4l to work with multiple > independent PHCs that would form a PTP clock (and rely on phc2sys to > sync those PHCs).
Doesn't my patch #2 do this? > This needs separation of struct clock into two > structures, as some fields are per-PTP clock and some are per-PHC. > I have a patch that does this but it needs to be rebased. You mean, the phc2sys 'struct clock', I guess? Please post the patch, so we see what you are talking about. > I think this is a prerequisite to having a boundary clock that uses > multiple PHCs, I cannot imagine how it could work without this > separation. So, in the current form, what does the 'automatic' mode (I mean, -a without -r) provide? Nothing useful? We can't do a release with half baked stuff like that. Thanks, Richard ------------------------------------------------------------------------------ _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
