On Thu, 24 Nov 2011, Tom Gundersen wrote: > It looks like my problem was something else. We don't do anything to > synthesize the ACPI HKEY events (AFAIK), so I believe that KDE (which > I am using) should be using the input events and that the HKEY stuff > does not matter. I have no idea if KDE can do it or not. > As to the original report about the change in HKEY events, this is > (probably) due to PROCFS_ACPI being disabled in the Arch kernel as of > 3.1. Well, maybe Arch needs to update its userspace to cope with its kernel... but still, we will only really know whether this is the problem or not if someone checks the input devices and the acpi events over netlink in that Arch kernel. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
