-
Maciej Lipinski authored
The fixed-latency mode was triggered in the case of receving incorrect timestamp. This was not correct. the incorrect_timestamp bit was not evaluated when arming fixed latency mechanism. This could cause an erronous timestamp to trigger fixed-latency mechanism
eadd9cca
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
fabric | ||
timing | ||
wr_dacs | ||
wr_eca | ||
wr_endpoint | ||
wr_mini_nic | ||
wr_nic | ||
wr_pps_gen | ||
wr_si57x_interface | ||
wr_softpll_ng | ||
wr_streamers | ||
wr_tbi_phy | ||
wr_tlu | ||
wr_txtsu | ||
wrc_core | ||
Manifest.py |