On Sat, Dec 12, 2009 at 09:13:01AM +0100, Stéphane Chatty wrote: > > Le 11 déc. 09 à 23:36, Dmitry Torokhov a écrit : > >> Hi Stephane, >> >> >>> +static int emulate_touchscreen = 1; >>> +module_param_named(emulate_touchscreen, emulate_touchscreen, int, >>> 0600); >>> +MODULE_PARM_DESC(emulate_touchscreen, >>> + "Touchscreen emulation on 3M multitouch panel (0=off, 1=on)"); >>> + >> >> I thought we agreed that this option is unnecessary. >> > > Well, actually I was unsure what the conclusion of your discussion was. I > decided that I would send this patch as is to see what happens :-) > > Here are our options: > 1) mix touchscreen emulation and multitouch at all times > 2) only activate touchscreen emulation when requested (module > parameter, or something else) > 3) have separate input nodes > 4) kill the touchscreen emulation code, let the higher layers do it if > necessary > > I personally would rule out option 4. The others are OK to me. Your > thoughts? #1 until everyone moves on to multitouch... and everyone means _everyone_, not only X and distributions. I could consider #3 if we see that multitouch data overwhelms oldish userspace, but OTOH users would probably prefer to update their userspace to take advantage of their hardware so the multitouch data will be opened anyway... so we back to #1. -- Dmitry -- 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
