You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I was wondering if I could get some help writing a driver for the Lexip NP93 mouse. I'm trying to use it for accessibility purposes as it would be ideal to play games with for people who only have use of one hand. Currently the mouse is using the hid-generic kernel driver when I plug it in. The mouse in question is a special mouse that has:
a dpi toggle button (doesn't work with hid-generic)
a joystick (Instead of analog input, it is mapped to button events when I use xev. Is this because hid-generic doesn't allow for extra analog input?)
RGB LED control
Regular mouse stuff like analog input for moving around and many buttons
Ideally this mouse would behave like a mouse with a joystick input. When I use wireshark on the usbmon device that is created I can see the bits that change when I press each button. However, the joystick seems to be registered as a button that only changes bits. I would love to get some help understanding which bits correspond to what when I'm looking at wireshark data.
I was wondering if someone could point me to an explanation of the interactions between the mouse kernel driver, the ratbagd c userspace driver and the ratbagd device config file. To get the functionality I want (analog input from the joystick) would I need to write a kernel driver as well as a ratbag userspace driver? What would the the process look like? I would love to contribute more if someone can help me get started.
The text was updated successfully, but these errors were encountered:
Hey, I was wondering if I could get some help writing a driver for the Lexip NP93 mouse. I'm trying to use it for accessibility purposes as it would be ideal to play games with for people who only have use of one hand. Currently the mouse is using the hid-generic kernel driver when I plug it in. The mouse in question is a special mouse that has:
Ideally this mouse would behave like a mouse with a joystick input. When I use wireshark on the usbmon device that is created I can see the bits that change when I press each button. However, the joystick seems to be registered as a button that only changes bits. I would love to get some help understanding which bits correspond to what when I'm looking at wireshark data.
I was wondering if someone could point me to an explanation of the interactions between the mouse kernel driver, the ratbagd c userspace driver and the ratbagd device config file. To get the functionality I want (analog input from the joystick) would I need to write a kernel driver as well as a ratbag userspace driver? What would the the process look like? I would love to contribute more if someone can help me get started.
The text was updated successfully, but these errors were encountered: