On Mar 19 2015 or thereabouts, Yves-Alexis Perez wrote: > On Thu, Mar 19, 2015 at 11:58:31AM -0400, Benjamin Tissoires wrote: > > On Mar 19 2015 or thereabouts, Yves-Alexis Perez wrote: > > Again, sorry, I thought I answered it. With the kernel patches applied: > > - disabled in the bios without psmouse.proto=imps -> touchpad still > > enabled, trackstick + buttons working > > - disabling in the bios + psmouse.proto=imps -> touchpad disabled, > > trackstick + buttons working > > - enabled in the bios + psmouse.proto=imps -> touchpad barely usable, > > trackstick + buttons working > > > > That should cover all the cases :) > > > Actually, one is missing: “touchpad enabled / without > psmouse.proto=imps”, but it doesn't really matter for me since I'm not > using the touchpad anyway. Yes, but that is the most used case, and if this one was not working then the patch series would have been moot :) > > But that also means if I want a disabled touchpad (without using xinput > disable) I'm forced to use psmouse.proto=imps. It does work fine but I > then lose the speed and sensitivity attributes (in > /sys/devices/platform/i8042/...) and the Trackpoint device itself is > gone from the input subsystem (everything goes to the touchpad one). > > I find that a bit confusing, and think it'd be best if the touchpad > disabling could be handled even when IMPS/2 is not used, but maybe it's > impossible to do? I honestly did not spent much time understanding the IMPS/2 boot option and the way it is advertised by the bios. I just made the above statements. To solve your problem, your desktop environment must have a "disable touchpad" switch in the configuration panel. At least, gnome has. This way, your settings should come back at each login. And if this is not sufficient enough, you can always add a xorg.conf.d snippet which disables the touchpad when X starts. Cheers, Benjamin > > Sorry for the ~user-related questions. > > Regards, > -- > Yves-Alexis -- 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
