On Fri, 15 Nov 2013 11:17:31 +0100 David Herrmann <dh.herrmann@xxxxxxxxx> wrote: > Hi Antonio > > On Fri, Nov 15, 2013 at 11:11 AM, Antonio Ospite > <ospite@xxxxxxxxxxxxxxxxx> wrote: > > On Fri, 1 Nov 2013 21:16:15 +0100 > > David Herrmann <dh.herrmann@xxxxxxxxx> wrote: > > > >> Motion sensors are getting quite common in mobile devices. To avoid > >> returning accelerometer data via ABS_X/Y/Z and irritating the Xorg > >> mouse-driver, this adds separate ABS_* bits for that. > >> > >> This is needed if gaming devices want to report their normal data plus > >> accelerometer/gyro data. Usually, ABS_X/Y are already used by analog > >> sticks, so need separate definitions, anyway. > >> > >> Signed-off-by: David Herrmann <dh.herrmann@xxxxxxxxx> > > > > Hi, what's the status of this patch? > > I cannot see it in Dmitry's repository, David maybe you have another > > repository I can pull from? > > Please see patch 1/13 and 2/13. They fix the kernel ABI to support new > ABS_* bits (the current ABI is broken in that regard). As this is > quite critical and caused breaks during the last merge-window, we > haven't merged it yet. I hope to get it into 3.14, though. The current > patches seem fine and work for me. I will try to get the user-space > part working in the next weeks. > > Any help is welcome! > I can try updating evtest, any idea about how I should check at runtime whether ABS_MAX2 is supported or not? Ciao, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
