On Thu, 2017-06-29 at 09:31 +0200, Pali Rohár wrote: > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > > > > <snip> > > > While policy normally belongs to userspace, I'd argue this is > > > workaround for a hardware bug, and in-kernel solution would be > > > acceptable. > > > > > > Anyway, disable attribute would be nice first step. > > > > It's already fixed for those of us on recent distributions. The > > "ID_INPUT_TOUCHPAD_INTEGRATION=internal" touchpads will be disabled > > when the lid is closed, when libinput is used to process the > > events. > > But this does not fix other usage of /dev/input/* and also does not > fix > pressing spurious keys in linux virtual tty (ctrl+alt+f1). So it is > not > a fix. > > Also important question is: How you detect which input device is > "internal", non-removable part of notebook and which one is external? We have heuristics and a database. Look at the hwdb/ subdirectory in systemd. > Maybe ACPI/DSDT provides some information? (No idea, just asking) It could and should, but it's usually empty because when some hardware makers can't be bothered to change the device's name, they'll hardly spend that time adding location information, are they? -- 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
