-
-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Add support for large Mouse Reports #16371
Conversation
@@ -165,11 +162,26 @@ const pointing_device_driver_t pointing_device_driver = { | |||
// clang-format on | |||
|
|||
#elif defined(POINTING_DEVICE_DRIVER_pimoroni_trackball) | |||
|
|||
mouse_xy_report_t pimoroni_trackball_adapt_values(clamp_range_t* offset) { |
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.
Was it intended to move this from pimoroni_trackball.c?
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.
Yeah. Wanted to move all the hid clamping stuff into the drivers file, as it's more appropriate there, I think.
Using the extended reports with the pimoroni trackball, does seem to produce a better feel to the device. I guess the reason for not making this the default is the extra firmware space required? |
That may be because it's not hitting the 127 limit, and generates a more natural feel. And yeah, also, not everything may support it, so opt in is better than opt out, until there are enough people using it to verify it's not an issue. |
74f88e8
to
e995e03
Compare
e995e03
to
1c7754f
Compare
+1 tested - makes pimoroni trackball significantly more accurate and smooth. |
It's probably worth adding this define to the documentation? |
1c7754f
to
07e0285
Compare
I had forgotten, actually. Added in 07e0285 |
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.
weak approval as I can't comment much on the usb descriptor changes other than it works.
Co-authored-by: Sergey Vlasov <[email protected]>
Co-authored-by: Ryan <[email protected]>
Co-authored-by: Ryan <[email protected]>
e7cbf1b
to
d8a055c
Compare
d8a055c
to
caebf93
Compare
Co-authored-by: Sergey Vlasov <[email protected]> Co-authored-by: Ryan <[email protected]>
Description
While looking at tmk stuff, I noticed that that they added support for 16-bit X and Y reports for mouse reports.
This expands the report to allow for int16_t to be used for the x and y axises, as well as boot mouse reports.
I suspect that the mouse boot protocol requires that the endpoint not be shared, but ... I'm not sure about that.
Types of Changes
Checklist