On Mon, 18 Nov 2013 10:38:42 -0500 Benjamin Tissoires <benjamin.tissoires@xxxxxxxxxx> wrote: > Hi guys, > > I forgot to say that: > - IMO, the approach raised in 2011 by Antonio[1] was the correct one: > the multitouch protocol introduced a regression with devices providing > large axis number, so we should fix this in input core, not on a per > device basis. > - I'll send an update to this patch later this week. Thanks. > - I don't think remapping the PS3 axis now will make into upstream > (backward compatibility), but this is only my own opinion What do other people think? I was going to motivate the change of keycodes with the fact that the device was not fully functional for a long time, but if you fix it in input core this argument does not hold anymore :) It would have been a good excuse to have a user of the full gamepad API and of a good part of the motion-tracking API, but I won't push this too hard. > - I have discussed this with the Xinput maintainer, and he also would > like to get the information from the kernel when the ABS_MT axis are > used as ABS_MT or ABS_MISC, so I'll also add a property in this way. > Thanks, 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
