-
Maciej Lipinski authored
When frames were sent to close to each other (high frequency), the timestamp of incoming frame would reset the delay counter of the previously received frame. This could potentially cause infinite fixed delay... Now, in such case, the counter is not reseted and so the following (too closely) frame will be exposed to the user immediatelly.
3e2985c4
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| fabric | ||
| timing | ||
| wr_dacs | ||
| wr_eca | ||
| wr_endpoint | ||
| wr_mini_nic | ||
| wr_pps_gen | ||
| wr_si57x_interface | ||
| wr_softpll_ng | ||
| wr_streamers | ||
| wr_tbi_phy | ||
| wr_tlu | ||
| wrc_core | ||
| Manifest.py |