On 18/11/13 11:25, Antonio Ospite wrote: > 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 :) Just FYI, I mentioned this because there already has been 2 or 3 threads regarding bad uses of keycodes/axis for gamepads (WII, XBox, and PS3 IIRC), and the result was always "we do not break user space". Personally, I have nothing against mapping the correct axis :) > > 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. There are some initiatives in the user space to fix those kernel problems. libinputmapper (find one of David Herrmann's post) and libevdev (on Freedesktop) are some good candidates. Cheers, Benjamin -- 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
