[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1603241527510.3656@cbobk.fhfr.pm>
Date: Thu, 24 Mar 2016 15:30:20 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Clément Vuchener <clement.vuchener@...il.com>
cc: Benjamin Tissoires <benjamin.tissoires@...hat.com>,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported
device
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,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists