-
Notifications
You must be signed in to change notification settings - Fork 6
Clarifications to Device specification and consistent terminology #197
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
Conversation
|
@bruno-f-cruz @Poofjunior I am trying to close here all outstanding issues with the device specification that you encountered when implementing the core.pico. The currently outstanding are: |
This is an alternative to explicitly specifying the length in the title while maintaining good readability in document TOC.
e15cac0 to
72652eb
Compare
bruno-f-cruz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small comment that we should address before making a 2.0 release, but otherwise lgtm
13953c3 to
fc55475
Compare
bruno-f-cruz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last pass, and otherwise we can merge.
1592658 to
64366fe
Compare
To ensure terminology remains consistent with the binary protocol specification, we replace "host" with "Controller" and standardize capitalization as required.
Outstanding clarifications to the device specification have also been included, some of them recovered from previously closed PRs which were lost during repository reorganization, e.g. #6.
Fixes #177
Fixes #47
Fixes #5
Fixes #4