[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM4jgCp5yPeRXHukGBLKYXOJev2VbrW5H4dREb_u=AX9vER_Tg@mail.gmail.com>
Date: Thu, 24 Mar 2016 16:19:28 +0100
From: Clément VUCHENER <clement.vuchener@...il.com>
To: Jiri Kosina <jikos@...nel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@...hat.com>,
linux-kernel@...r.kernel.org,
linux-input <linux-input@...r.kernel.org>
Subject: Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device
2016-03-24 15:30 GMT+01:00 Jiri Kosina <jikos@...nel.org>:
> On Wed, 23 Mar 2016, =?UTF-8?q?Cl=C3=A9ment=20Vuchener?= wrote:
>
>> So, I decided to move all USB related features in user-space (as far as
>> I know, I was the only user, but if someone is looking for a
>> replacement, I wrote a small tool available here:
>> https://github.com/cvuchener/corsair-usb-config). This simplification
>> only leaves the usage code remapping part and the driver no longer
>> depends on USB and LED subsystems. This should make the driver easier to
>> maintain or to add new supported devices.
>
> While you are performing this move, is there anything that's actually
> preventing you from doing the remapping from userspace as well?
>
> HID subsystem has for long time been providing the setkeycode() hook for
> remapping usages, and udev (well, more precisely, that s*****d thing) is
> actually shipping a lot of hw-specific remap data these days.
Thanks for the tip, is it possible to ignore some usages with this
method (done in the default case)?
>
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
Powered by blists - more mailing lists