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

Non-blocking device file may be causing invalid captured buffer #32

Open
vladimirvivien opened this issue Oct 18, 2022 · 0 comments
Open

Comments

@vladimirvivien
Copy link
Owner

Currently, the a device is opened as non-blocking and the code uses select to be notified of buffer readiness. This appears to cause incomplete or incorrect buffers to be returned. This could be due to the driver still writing while buffer is being read. The current workaround has been to copy the buffer before making it available for use.

Explore other approaches including blocking read, DMA, or direct device reads or make them all available at some point and let developer select which work best for device being tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant