Thanks for the quick reply, I was more afraid that changing the phc to not be expected to be in the pattern /dev/ptp% and to remove the phc_get_caps check would find more resistance. I can make a new patch with your suggestion and get back to you.
Thanks! Dimitrios On Wed, Nov 7, 2018 at 4:07 PM Richard Cochran <richardcoch...@gmail.com> wrote: > On Wed, Nov 07, 2018 at 03:16:22PM +0100, Dimitrios Katsaros wrote: > > However, there is one issue for this setup to work correctly: fd clock > > support is limited. The kernel does provide the ability to implement your > > own POSIX clocks, but the daemons providing ptp clock support do not have > > the ability to synchronize any system based POSIX clock, just the > standard, > > predefined clocks. > > The ptp4l program already has a command line option to specify the > PHC. Currently this is required to match the PHC associated with the > network interface. A minor change is needed to allow a different > clock. > > So why not simply use the '-p' option? > > Initially, before we had the ethtool interfaces, this was needed to > specify the PHC, but today the option is useless. > > We can change the code to relax the restrictions on the passed > character device node path. > > Thanks, > Richard > >
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
