Ah and one more clarification, Because my device is reprisented using the POSIX interface, i do not support the phc_get_caps option. if I were to use the -p option to pass any clock, I would have to change this to something more basic, like I was doing in the posix_open function, where I was instead checking for the clock_gettime syscall. Would that be an acceptable solution?
Regards, Dimitrios On Wed, Nov 7, 2018 at 4:07 PM Richard Cochran <[email protected]> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
