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.

Sign up for GitHub

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

Jump to bottom

Manage our own Serial #132

Closed
amcjen opened this issue Jun 5, 2014 · 2 comments
Closed

Manage our own Serial #132

amcjen opened this issue Jun 5, 2014 · 2 comments

Comments

@amcjen
Copy link
Member

amcjen commented Jun 5, 2014

We need to remove serial from Bitlash, and handle it ourselves.

Also we should move to use Serial interrupts for non-blocking
@matthijskooijman matthijskooijman mentioned this issue Jun 30, 2014
Merged
@matthijskooijman
Copy link
Collaborator

I still have a big change for bitlash pending, which I haven't spent any more time on in the last months. I should clean that up again and get them merged by Bill (See billroy/bitlash#31 and billroy/bitlash#23).

@matthijskooijman matthijskooijman mentioned this issue Jul 3, 2014
Open
5 tasks
@matthijskooijman
Copy link
Collaborator

This was implemented by Jeremie, we now have our own serial loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amcjen @matthijskooijman