Skip to content

Conversation

@martinxyz
Copy link

When all block buffers are in use, some waiting loops store (block_buffer_head+1)
before the loop starts, under the assumption that no other code can add a block
to the buffer. Which is kind of correct. But if an instant-stop did happen during
such a loop it got stuck there forever.

When all block buffers are in use, some waiting loops store (block_buffer_head+1)
before the loop starts, under the assumption that no other code can add a block
to the buffer. Which is kind of correct. But if an instant-stop did happen during
such a loop it got stuck there forever.
@martinxyz
Copy link
Author

martinxyz commented Dec 29, 2018

We noticed this in our fablab. The fix was tested&verified in my pulseraster fork (https://github.com/martinxyz/LasaurApp), but since the affected firmware code in this repo looks the same I'm submitting it here.

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

Successfully merging this pull request may close these issues.

1 participant