On Tue, 15 Dec 2009, Stefan Bader wrote: > >>> This might be an overly naive approach (or call it thinking loudly)... > >>> It would probably break a lot of stuff when the JOYSTICK/TRIGGER block > >>> moved to the 0x210 region, but would it be a solution to have a block > >>> of additional joystick buttons there and check on assigning buttons to > >>> a joystick, whether it traverses over to GAMEPAD and in that case skip > >>> to the additional block? > >> That's what we have to do I guess... I wonder how many keycodes will we > >> need so we won't have to split the region again? Will they come up with > >> 70 buttons next time? > > > > Yup, I am not able to come up with anything more clever either. > > > > I can do that easily ... any suggestions for button names? :) > > > #define BTN_TRIGGER_HAPPY01 0x210 > ... > #define BTN_TRIGGER_HAPPY40 0x238 > > :-P Assuming 40 additional buttons should be crazy enough (but I know > this has been said before about other things). Dmitry, do you have any preference here yourself? -- Jiri Kosina SUSE Labs, Novell Inc. -- 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
