Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-07 Thread David Herrmann
Hi On Mon, Oct 7, 2013 at 3:30 AM, Peter Hutterer wrote: > On Sun, Oct 06, 2013 at 05:04:36PM -0700, Dmitry Torokhov wrote: >> Peter Hutterer wrote: >> >On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: >> >> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: >> >> >

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-07 Thread David Herrmann
Hi On Mon, Oct 7, 2013 at 3:30 AM, Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Oct 06, 2013 at 05:04:36PM -0700, Dmitry Torokhov wrote: Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: On Fri, Oct 04, 2013 at

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Peter Hutterer
On Sun, Oct 06, 2013 at 05:04:36PM -0700, Dmitry Torokhov wrote: > Peter Hutterer wrote: > >On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: > >> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: > >> > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote:

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Dmitry Torokhov
Peter Hutterer wrote: >On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: >> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: >> > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: >> > > As we painfully noticed during the 3.12 merge-window our >> > >

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Peter Hutterer
On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: > On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: > > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: > > > As we painfully noticed during the 3.12 merge-window our > > > EVIOCGABS/EVIOCSABS API is

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Dmitry Torokhov
On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: > > As we painfully noticed during the 3.12 merge-window our > > EVIOCGABS/EVIOCSABS API is limited to ABS_MAX<=0x3f. We tried several > > hacks to work around it but

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Dmitry Torokhov
On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: As we painfully noticed during the 3.12 merge-window our EVIOCGABS/EVIOCSABS API is limited to ABS_MAX=0x3f. We tried several hacks to work around it but if we

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Peter Hutterer
On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: As we painfully noticed during the 3.12 merge-window our EVIOCGABS/EVIOCSABS API is limited to

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Dmitry Torokhov
Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: As we painfully noticed during the 3.12 merge-window

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-06 Thread Peter Hutterer
On Sun, Oct 06, 2013 at 05:04:36PM -0700, Dmitry Torokhov wrote: Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote: On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote: On Thu, Oct 03, 2013 at 12:10:36AM +0200, David

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-03 Thread Peter Hutterer
On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: > As we painfully noticed during the 3.12 merge-window our > EVIOCGABS/EVIOCSABS API is limited to ABS_MAX<=0x3f. We tried several > hacks to work around it but if we ever decide to increase ABS_MAX, the > EVIOCSABS ioctl ABI might

Re: [RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-03 Thread Peter Hutterer
On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote: As we painfully noticed during the 3.12 merge-window our EVIOCGABS/EVIOCSABS API is limited to ABS_MAX=0x3f. We tried several hacks to work around it but if we ever decide to increase ABS_MAX, the EVIOCSABS ioctl ABI might

[RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-02 Thread David Herrmann
As we painfully noticed during the 3.12 merge-window our EVIOCGABS/EVIOCSABS API is limited to ABS_MAX<=0x3f. We tried several hacks to work around it but if we ever decide to increase ABS_MAX, the EVIOCSABS ioctl ABI might overflow into the next byte causing horrible misinterpretations in the

[RFC] Input: introduce ABS_MAX2/CNT2 and friends

2013-10-02 Thread David Herrmann
As we painfully noticed during the 3.12 merge-window our EVIOCGABS/EVIOCSABS API is limited to ABS_MAX=0x3f. We tried several hacks to work around it but if we ever decide to increase ABS_MAX, the EVIOCSABS ioctl ABI might overflow into the next byte causing horrible misinterpretations in the