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

Improve logging #48

Open
misson20000 opened this issue Sep 28, 2018 · 0 comments
Open

Improve logging #48

misson20000 opened this issue Sep 28, 2018 · 0 comments
Milestone

Comments

@misson20000
Copy link
Owner

Blocked on #47.

Currently, every call to printf in Twili blocks on a USB transfer. There should be several different logging modes:

  • USB Synchronous: Each call to printf blocks until the data is received by twibd. Useful for debugging.
  • USB Asynchronous: When printf is called, if we are waiting on a USB transfer, queue the message and submit another transfer when that one completes. Otherwise, submit a new transfer and don't want for it to complete. Should be more performant than synchronous.
  • Transfer: printf appends to a ringbuffer that can be read out via a bridge request. Useful for when USB logging isn't an option, or when it's not important that logs be transferred out-of-band. This mode should never block.
@misson20000 misson20000 added the enhancement New feature or request label Sep 28, 2018
@misson20000 misson20000 added this to the v1.1.0 milestone Sep 28, 2018
@misson20000 misson20000 removed the enhancement New feature or request label Sep 28, 2018
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