receive(): don't touch FIFO on timeout #98
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix dramatically reduces lost packages when polling for packets.
Consider this use case:
If a packet arrives partially just before the timeout kicks in, the packet is lost because the receive-method switches to idle, clears the queue and the interrupt. This patch does not do and just returns, so the next iteration will pick up the packet.
Note that the problem is independent of the actual value of
timeout, because with any timeout-value you can run into this problem. The problem is more prominent with low bitrates, since transfers take much longer and therefore the chance of hitting the timeout is much higher.The new combined library has the same problem I think, but I did not test because my application still uses this library.