On Wed, 2013-12-04 at 18:40 +0100, Richard Cochran wrote: > On Tue, Dec 03, 2013 at 09:33:21PM +0000, Keller, Jacob E wrote: > > > > I like this idea. I also think if we supported the "push" updates from > > ptp4l, where ptp4l sends data over the management interface it would > > enable the phc2sys to update it's internal state without requiring > > polling as it could update whenever it receives data on the management > > socket. > > Right, I like the push idea too, and for me it has higher priority > than removing the static port array.
I was thinking about ways to implement push-based messages... What do you think about having an extended message which indicates "I am ready to receive".. then once ptp4l gets this, it then starts pushing a set of notifications on events. I like this better than a configuration option, since it means ptp4l only sends messages on the uds when some management interface has requested it... Thoughts? It also doesn't seem too difficult to implement.. I haven't had time yet to try my hand at something, but I just wanted to see if we could hash out implementation that we think is right. Regards, Jake ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
