linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Clément VUCHENER" <clement.vuchener@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-kernel@vger.kernel.org,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device
Date: Thu, 24 Mar 2016 16:19:28 +0100	[thread overview]
Message-ID: <CAM4jgCp5yPeRXHukGBLKYXOJev2VbrW5H4dREb_u=AX9vER_Tg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1603241527510.3656@cbobk.fhfr.pm>

2016-03-24 15:30 GMT+01:00 Jiri Kosina <jikos@kernel.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
>

  reply	other threads:[~2016-03-24 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 17:32 [PATCH 0/2] hid: corsair: Driver simplification and new supported device =?UTF-8?q?Cl=C3=A9ment=20Vuchener?=
2016-03-23 17:32 ` [PATCH 1/2] HID: corsair: Remove all features using the USB protocol =?UTF-8?q?Cl=C3=A9ment=20Vuchener?=
2016-03-23 17:33 ` [PATCH 2/2] HID: corsair: Add K40 support =?UTF-8?q?Cl=C3=A9ment=20Vuchener?=
2016-03-24 14:30 ` [PATCH 0/2] hid: corsair: Driver simplification and new supported device Jiri Kosina
2016-03-24 15:19   ` Clément VUCHENER [this message]
2016-03-29 13:52     ` Jiri Kosina
2016-03-24 14:37 ` Benjamin Tissoires
2016-03-24 14:42   ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM4jgCp5yPeRXHukGBLKYXOJev2VbrW5H4dREb_u=AX9vER_Tg@mail.gmail.com' \
    --to=clement.vuchener@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).