> now I looked deeply at your problem. I read that part of ACPI code and > it really looks like that NEVT method does not handle all possible > events. Thank you for taking your time to review my findings. > But how can windows driver handle that? In my opinion it either do some > init magic so NEVT will receive event with mask 0x0800 or it overwrite > some ACPI method and handle it locally... I have no idea, but Kyle Evans had a few in a message I referenced earlier in this thread [1]. > You can try to play with overwriting ACPI function NEVT at runtime and > patch it to call WMIA also for other masks. I already tried that before writing the first message in this thread, which includes the following quote: "However, even when I customized the NEVT method to call WMIA for values 0x1000 and 0x2000, the dell-wmi driver reported all zeros for the event data retrieved using _WED." > Are you 100% sure that keypress is not sent to i8042 controller and that > linux kbd driver does not filter it somehow? Ideally test events with > userspace application input-events and not with some X utility (to be > sure that X does not consume that keypress too). Yes, I'm sure. First I booted the kernel with i8042.debug=1. Interrupts were raised as expected for hotkey #2, but not for hotkey #3. Then I enabled CONFIG_INPUT_EVBUG. As expected, events were generated for hotkey #2, but not for hotkey #3. [1] http://www.spinics.net/lists/linux-acpi/msg34577.html -- Best regards, Michał Kępień -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
