<html><head></head><body>ps: a different clock domain requires a dedicated GM. 1588 and 802.1AS are seperate clock domains. <div class="gmail_quote">Am 24. Juni 2019 16:13:05 MESZ schrieb Chris Caudle <chris@chriscaudle.org>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class="k9mail">On Mon, June 24, 2019 6:46 am, Christoph Kuhr wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> What is the need for a specific GM if you AVB switch is down? Thus, one of the AVB switches involved should be the GM. The "core-most" switch in particular. Or can someone think of a scenario, where this does not make sense? </blockquote> If you have a higher quality device (for example a network master clock connected to GPS disciplined oscillator for high stability). In that case the device should advertise a higher quality and should be selected as master clock in any case. One other case which comes to mind is if you want a multi-protocol device to be master for a mixed system, so a single device providing synchronized 802.1AS for AVB devices, and layer 3 1588 messages for layer 3 devices. Definitely starts getting into specialized cases, and you should be able to set the clock quality field on a specialized clock source like that so that it always wins the best master clock vote. </pre></blockquote></div> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</body></html>