On Fri, 2009-03-06 at 10:09 +0000, Matthew Garrett wrote: > > > > How will it interact with software stacks like HAL when the lock button > > > > is pressed? > > > I don't really understand the question? > > It was more: will events come out of both the notify method *and* > > the /proc/acpi/toshiba/keys stuff, or will they only come out of the > > notify method if it can be enabled? (I'm just trying to establish that > > things polling /proc/acpi/toshiba/keys won't end up causing duplicated > > events). > Either the kernel or userspace will get the event, but not both. There's > an argument for disabling the input code if /proc/acpi/toshiba/keys is > open in order to avoid breaking anything that expects to get the code > itself. I see. One other thing occurred to me. Is there any way for Hal to know that the notify stuff is in place and thus doesn't need to poll /proc/acpi/toshiba/keys? Otherwise it's going to poll it anyway which fails to remove the periodic wakeups. D. -- Daniel Silverstone http://www.simtec.co.uk/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
