Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ether driver receive handling #16

Open
HirokiIshiguro opened this issue Aug 28, 2019 · 2 comments
Open

Ether driver receive handling #16

HirokiIshiguro opened this issue Aug 28, 2019 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@HirokiIshiguro
Copy link
Member

Describe the bug
If user would set descriptor num to 2 or more, receive process would be corrupted.
If user would set descriptor num to 1, receive process would not be corrupted.
This is just reported, SheltyDog has not understood this mechanism.

Expected behavior
No corrupting.

Screenshots or console output
None.

To reproduce

  • set descriptor num to 2 or more.

Code to reproduce the bug

  • no need. (current code can reproduce)

Additional context
None.

@HirokiIshiguro HirokiIshiguro added the bug Something isn't working label Aug 28, 2019
@HirokiIshiguro HirokiIshiguro self-assigned this Aug 28, 2019
@09fox
Copy link
Member

09fox commented Aug 28, 2019

This may be because the receiving task processes only one packet per notification.

If two or more packets are received before the interrupt handler is activated and notified to the receiving task, the second and subsequent packets are delayed without being processed until the next notification occurs because receiving task processes only one packets .

@HirokiIshiguro
Copy link
Member Author

Thanks a lot. I will fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants