On Fri, Mar 06, 2009 at 10:04:21AM +0000, Daniel Silverstone wrote: > On Fri, 2009-03-06 at 09:56 +0000, Matthew Garrett wrote: > > Yes, it'll be as functional as it was previously. They can be remapped > > on machines that have a different keymap. > > Since I don't understand the input layer well enough yet, can you > confirm if it is possible to add new mappings in without changing the > source? I.E. if laptop <foo> has another hotkey not yet considered, is > it just an FDI for hal, or is it a source change in the kernel? Yes, the remapping can be done from userspace. > > > 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. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
