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

live: kill the second battery node created by wacom.ko #85

Open
bentiss opened this issue Feb 13, 2018 · 2 comments
Open

live: kill the second battery node created by wacom.ko #85

bentiss opened this issue Feb 13, 2018 · 2 comments
Labels
live mode

Comments

@bentiss
Copy link
Collaborator

bentiss commented Feb 13, 2018

There is one battery node for the bluez connection, which works, and one for the uhid device, which seems to be superfluous.
Track down who creates it and how to kill this from our uhid node.
@bentiss bentiss mentioned this issue Feb 13, 2018
Merged
7 tasks
@bentiss
Copy link
Collaborator Author

bentiss commented Feb 14, 2018

grmbl, this is because we are declaring the device as a bluetooth one:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/hid/wacom_wac.c?id=61f14c015f5be9151ba25e638d349f4d40cb7cd4#n3302

@bentiss
Copy link
Collaborator Author

bentiss commented Feb 14, 2018

One solution could be to use a different vendor ID than Wacom 0x056a (according to https://electronics.stackexchange.com/a/215605, wacom also owns 0x0531), but then, hid-generic doesn't create the input node. Fixable but requires more changes in the report descriptor.

@whot whot added the live mode label Jul 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
live mode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whot @bentiss