Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

On Thu, 24 Mar 2016, Clément VUCHENER wrote: > Thanks for the tip, is it possible to ignore some usages with this > method (done in the default case)? mapping to 0xff is a bit hackish way to achieve this. -- Jiri Kosina SUSE Labs

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

On Thu, 24 Mar 2016, Clément VUCHENER wrote: > Thanks for the tip, is it possible to ignore some usages with this > method (done in the default case)? mapping to 0xff is a bit hackish way to achieve this. -- Jiri Kosina SUSE Labs

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

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

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

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

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

On Thu, 24 Mar 2016, Benjamin Tissoires wrote: > I would say you can not do this this way. Even if you believe you are the > only user of the API, there might be someone who uses it, and you will end > up breaking his keyboard. > > Jiri will correct me, but the proper way to follow is to mark

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

On Thu, 24 Mar 2016, Benjamin Tissoires wrote: > I would say you can not do this this way. Even if you believe you are the > only user of the API, there might be someone who uses it, and you will end > up breaking his keyboard. > > Jiri will correct me, but the proper way to follow is to mark

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

Hi Clément, On Mar 23 2016 or thereabouts, =?UTF-8?q?Cl=C3=A9ment=20Vuchener?= wrote: > I tried to add support for the K40 some time ago, but the vendor specific USB > protocol became over-complicated because of a lot of small differences > between the K90 and the K40. Also, since I wrote the

Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device

Hi Clément, On Mar 23 2016 or thereabouts, =?UTF-8?q?Cl=C3=A9ment=20Vuchener?= wrote: > I tried to add support for the K40 some time ago, but the vendor specific USB > protocol became over-complicated because of a lot of small differences > between the K90 and the K40. Also, since I wrote the

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: >

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: >

[PATCH 0/2] hid: corsair: Driver simplification and new supported device

I tried to add support for the K40 some time ago, but the vendor specific USB protocol became over-complicated because of a lot of small differences between the K90 and the K40. Also, since I wrote the first version of this driver, I learned that USB control transfers could be done from

[PATCH 0/2] hid: corsair: Driver simplification and new supported device

I tried to add support for the K40 some time ago, but the vendor specific USB protocol became over-complicated because of a lot of small differences between the K90 and the K40. Also, since I wrote the first version of this driver, I learned that USB control transfers could be done from