On Sat, Mar 10, 2018 at 02:38:18AM +0100, Peter Schneider wrote:
> 1) ph2c2sys uses in "autodetect" (-a -r) or "wait for ptp4l" (-w) mode
> pmc-functionality to do his job. Unfortunately, the constant value "0" is
> used for the transportSpecific parameter, which is wrong for 802.1AS, and
> thus avoids using these modes successfully in phc2sys.
> I added an optional parameter to phc2sys ("-T 1"), which passes the 802.1AS
> conformant value to the used pmc-functionality to make phc2sys work correct
> for 802.1AS.I don't want to add yet another command line option to phc2sys. The way forward for that program is to add '-f config' and enable the long options, like in ptp4l and the new nsm. But that would be a new feature and not really a bug fix. It is something we can add following 1.9. > 2) When using layer 2 for management via pmc command, the management PDUs > are sent to further devices via the multicast address 01:1B:19:00:00:00, > which doesn't work for 802.1AS. (Strictly speaking, management messages aren't allowed in 802.1AS! But of course this should work.) > I made a quick solution which isn't usable publicly this way, but works for > me: I read in and use a config file (to be precise: the very same which I > use for ptp4l). Might be made more general usable by respecting the priority > of command line parameters. Right. The pmc program could also benefit from '-f config' and long options. Again, that is something new that will have to wait. Looking ahead, I have got some major new functionality lined up, and so the *next* release after is coming sooner rather than later. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
