The reason why I was asking is that some protocols like AVB provide the clock master ID and domain number with the stream description.
The slave is supposed to sync to the given master and domain rather than to the best one. This of course will be fully exploited only in non-trivial networks, where multiple masters are present. I'm thinking of the following slave set-up: by default it runs ptp4l with a reasonable config (i.e. the best master algorithm) and on stream reception it reconfigures ptp4l to the required master and domain number, using the local UDS. Once the domain number configuration and acceptable masters table are implemented, this should be possible. Petr On 17/05/17 10:52, Miroslav Lichvar wrote: > On Tue, May 16, 2017 at 10:26:01PM +0200, Petr Kulhavy wrote: >> How is it with domain number? Does the domainNumber limit the slave to >> operate only in that particular domain? >> Can the domainNumber be changed in runtime using pmc? > If there is command to switch the domain in run time, what will decide > the domain needs to be switched? > > If you need the system to be resilient against failures, it might be > better to run multiple slaves in different domains at the same time > and use for synchronization of the system clock only those that agree > with each another or with other time sources like NTP. It is > recommended by the Enterprise profile. You can easily do this with the > timemaster program from linuxptp. > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
