On Tue, 3 Dec 2013 20:27:46 +0100, Richard Cochran wrote: > You mentioned that you want to implement "hot pluggable" ports on top > of this series. Do you have anything yet? If so, please post that too, > so we can get the big picture.
Not yet, I'm working on it but there's still a long road ahead. My main motivation is to support bonding (which probably sounds scarier than it actually is), or alternatively, some other sort of automatic failover. I'm currently experimenting with multiple PHC support, which is needed for the above and, perhaps more interestingly, would allow things like boundary clock with separate NICs. Of course, for this to be fully useful, phc2sys will need to be extended to follow ptp4l's state machine for individual interfaces. IIRC Jake expressed interest in such phc2sys extension, too (http://sourceforge.net/mailarchive/message.php?msg_id=31176225). (I'm aware that boundary clock with separate but synchronized clocks is kind of out of PTP spec but I think it could be done in the way that's indistinguishable from the single clock from the other device's point of view, which is what really matters. There will be some impact on precision, of course.) Jiri -- Jiri Benc ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
