26 Jun
2019
26 Jun
'19
1:38 a.m.
Of course. GPS sync, forgot about that.
But for multi protocol, you should use a proxy GM for 1588. Meaning the device is synced
via 802.1AS and provides l3 sync for other 1588 devices. What do you think?
Aren't we always talking about specialized cases? ;-)
Am 24. Juni 2019 16:13:05 MESZ schrieb Chris Caudle <chris(a)chriscaudle.org>rg>:
On Mon, June 24, 2019 6:46 am, Christoph Kuhr wrote:
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
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?
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.
--
Chris Caudle
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org