data: add G Pro X Wireless Superlight #1122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Support for this receiver, and for the device using the powerplay receiver, still needs to be added to the kernel driver. For now, you can used the wired connection to configure the device. You should also not try to use with the powerplay receiver as the kernel driver does not support the connection and won't forward any input events to userspace. Signed-off-by: Filipe Laíns <lains@riseup.net>
|
@bentiss, you may want to be aware of this behavior. Essentially the kernel driver trips when trying to determine the connection type and won't forward any events to userspace because it does not know how to handle the connection. This is fine on the receiver that came with the device, as we will add support for that receiver together with the new connection type. But for receivers that support multiple types, which right now it's only the powerplay mat, that won't happen. In which case the user could just use the receiver that came with the device, or blocklist the kernel driver. I am not really sure how to handle this, I will have to have look at the driver. |
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Jan 29, 2021
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
|
I own this mouse and would very much like to start configuring it with piper asap 🙂 Edit: Just used this file and it works great! |
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Jan 31, 2021
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Feb 1, 2021
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Feb 2, 2021
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
FFY00
added a commit
to FFY00/linux
that referenced
this pull request
Feb 7, 2021
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
|
Are those logitech-dj patches still trying to be upstreamed? Are they still applicable to 5.13? |
|
The one adding the new receiver hasn't been upstreamed yet, the one fixing device when connected to a Powerplay mat is. Currently, the device only works with libratbag when connected via USB directly. |
|
Ok thanks, I can confirm it works via USB (would like to see the battery level also like I could on my G503). I was just checking if there was news since the last notes I could find on LKML were from early march for the 5.11 cycle. |
|
Should this be working yet? I'm not sure if I'm doing something wrong or I just misunderstood what has been said in the discussion. I am able to use the mouse with the provided Lightspeed receiver and directly over USB but I get no connection to the Powerplay receiver. Shouldn't it be working through the Powerplay receiver as well now? |
|
There was kernel bug regarding this, fixed in torvalds/linux@fab3a95. Which kernel are you running? |
|
Should have included that right away, of course. I'm running Linux 5.15.2-2, mouse is Pro X Superlight. When the Powerplay mat is plugged in, Piper shows a 404 image. |
|
I have done some basic testing now but can not figure out what is wrong. The device shows up in Solaar with charge, DPI and such but the mouse does send any input. I can also unpair the mouse from Solaar, which causes the Powerplay pad to enter pairing mode and when I restart the mouse, it gets paired again. Piper still only shows the 404 image but I can change the LED color from the LED tab. |
@SebbeM Did you ever get this figured out? Currently experiencing same issue. |
|
Yes, I thought that I should return and update on the issue but I am a bad person. When I updated the kernel to version 5.17.9-1, it all started working properly. I can't be completely sure that nothing else updated at about the same time but I think it was the kernel update that did it. I'm running Manjaro, if that matters. |
Im running Manjaro with 5.17 kernel, but Piper wont recognize my Logitech G Pro X Wireless Superlight. What Piper package version is working for you? |
|
I'm running version 0.6-2, installed from official repositories, packaged by Felix Yan. |
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Mar 19, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Mar 26, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 7, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 8, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
|
I have this mouse with this receiver and I can't wait for this commit to get accepted |
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 15, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 15, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Nov 25, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Nov 25, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Dec 12, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Dec 24, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Dec 29, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Dec 30, 2023
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jan 17, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jan 17, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jan 28, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jan 28, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
Cyanoxygen
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Feb 3, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Feb 6, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Feb 17, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
cthbleachbit
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Feb 29, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Feb 29, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Mar 11, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 6, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 8, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 10, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 10, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 18, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Apr 30, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
May 6, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
May 13, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
May 18, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
May 26, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
May 26, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jun 1, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jun 3, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
MingcongBai
pushed a commit
to AOSC-Tracking/linux
that referenced
this pull request
Jun 17, 2024
Tested with the G Pro X Superlight. libratbag sees the device, as expected, and input events are passing trough. libratbag/libratbag#1122 The receiver has a quirk where the moused interface doesn't have a report ID, I am not sure why, perhaps they forgot. All other interfaces have report IDs so I am left scratching my head. Since this driver doesn't have a quirk system, I simply implemented it as a different receiver type, which is true, it just wouldn't be the prefered approach :P Signed-off-by: Filipe Laíns <lains@riseup.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for this receiver, and for the device using the powerplay
receiver, still needs to be added to the kernel driver. For now, you can
used the wired connection to configure the device.
You should also not try to use with the powerplay receiver as the kernel
driver does not support the connection and won't forward any input
events to userspace.
Signed-off-by: Filipe Laíns lains@riseup.net