Tortue Posted April 22, 2013 Share Posted April 22, 2013 Hi. I just got a K90. I have written Linux input drivers before, and I can do it again. It would be easier and faster if I got an SDK from Corsair (uh, please? I'm willing to sign an NDA, as long as it doesn't prevent me from releasing opensource drivers). Input drivers in Linux live in userspace and communicate with a "character device driver" in the kernel, so the perl script posted here is actually a reasonable start. But I'll resort to writing a special driver for it only if I can't find a way to configure the existing drivers to work for it -- it's much easier to get lines added to distribution's configuration files (and they'll be maintained there) than to get a new program added to distros for a single device. The K90 is registering itself as 2 USB devices. All but 3 of the G-keys are registering with the same keycode, and the three exceptions are giving wrong answers (delete, scroll down, and something else). I'm also getting bogus signals from the mode keys (one of them is giving two backspaces!) and windows lockout key. I can disambiguate them based on signals arriving from the other 'USB device', but doing it via trial-and-error with no real info is going to be a pain in the tush. xev is your friend for getting keycodes and mouse buttons from unusual devices. But Figuring out what control signals to send to the keyboard (for backlighting controls, software mode switches, access to its memory, or just to get its cap lock and scroll lock lights working: why the heck are those standard things not working??) is a bit harder. Multimedia controls (while fairly limited on the K90) are already working great and got automapped by the default drivers. But the major reasons I got it were for the mx keyswitches and mode-switched macro keys; I'm a writer and a programmer, so I want them both to preserve my hands from RSI. I will use up 56 macros in no time flat. You thought gamers had use for a lot of macros? Programming, my friends, wants even more. So that's the reason it's worth my time to make this thing fully supported. Any help or info Corsair can offer would be greatly appreciated and will make the whole project go faster. Tortue Link to comment Share on other sites More sharing options...
DungeonLord Posted April 26, 2013 Share Posted April 26, 2013 i'm very excited about this. especially since steam and valve are starting to port their games to linux Link to comment Share on other sites More sharing options...
bjk Posted April 27, 2013 Share Posted April 27, 2013 xev is your friend for getting keycodes and mouse buttons from unusual devices. But Figuring out what control signals to send to the keyboard (for backlighting controls, software mode switches, access to its memory, or just to get its cap lock and scroll lock lights working: why the heck are those standard things not working??) is a bit harder. I have a K60 and have the problem that the \ and SHIFT+\ key repeats in Linux. I've found funny output from usbmon (kernel module) but can't make sense of it. All other keys work as they should (after the 1.31 firmware update that is). Corsair knows that it is a Linux specific problem but don't seem to have it as a priority about fixiing it. A shame since in Unix world the pipe | is used extensively. Link to comment Share on other sites More sharing options...
nurow Posted July 2, 2013 Share Posted July 2, 2013 Hi Tortue, did you ever make any progress with this? I'm looking for such a driver. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.