Hello everyone,
while debugging my 802.1AS endpoint I recognized that the servo was idle
after the first step.
It stopped processing sync messages until the next peer delay was measured.
The reason is that t3 is reset after the first step letting
tsproc_update_offset() fail.
I think tsproc_update_
On Mon, 2017-04-03 at 09:20 +0200, Burkhard Ilsen wrote:
> Hello everyone,
>
Hi,
Just FYI, this mailing lists preference is to send plain-text emails if
possible.
> while debugging my 802.1AS endpoint I recognized that the servo was
> idle after the first step.
> It stopped processing sync mess
On Mon, Apr 03, 2017 at 09:20:44AM +0200, Burkhard Ilsen wrote:
> The reason is that t3 is reset after the first step letting
> tsproc_update_offset() fail.
You mean the call to tsproc_reset() after SERVO_JUMP...
> I think tsproc_update_offset() should not fail in this case because the
> filtered
