[riot-notifications] [RIOT-OS/RIOT] drivers/rail: efr32 radio driver (#9212)

Martine Lenders notifications at github.com
Thu Jan 10 10:19:13 CET 2019


> That is interesting. Is there a timeout for the fragmentation?
> I mean there is still the problem of a relativ ~30-40ms delay (first packet even >200ms) between the arrival and processing of a packet by the driver and the first call of the recv-function by the upper netdev layer. Could this be the problem?

The fragmentation just is best effort. When a fragment is sent, the rest is requeued by the 6Lo thread and once the message is dequeued again the next fragment is sent. Usually, this happens when for some reason the TX buffer is not ready yet. We had a similar problem in #10268. @SemjonKerner do you remember how we solved this without #10403?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/9212#issuecomment-453025281
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190110/32eb1b4e/attachment.html>


More information about the notifications mailing list