On Thu, Aug 12, 2010 at 11:42 AM, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote: > On Wed, 2010-08-11 at 15:51 +0200, Corentin Chary wrote: >> And you should probably make it a platform driver (being the parent of >> acpi, wmi, input, backlight, rfkill, etc..). >> >> Is there a lot of thing hidden in ACPI / WMI on these models (like >> hotkeys, backlight, light sensors) ? > > I hooked up something (below) to dump the AE or IO WMI blocks each time > we get a notification on the VPC2004 device. Although the notification > happens when we press a key, nothing ever changes in either of them. They is probably something interesting in the u32 event var. To get wmi events, you need to use wmi_install_notify_handler. For example, the hardware rfkill state may change due to some keypress, and an event may be sent via acpi or wmi, but if you don't catch it, the rfkill class won't be updated. Could you send the output of acpidump ? > I *did* notice that we're actually getting proper keycodes for the > hotkeys though, so for now I've lost what little interest I already had > in doing anything with WMI. If anyone (Florian?) wants to do more, I'd > be happy to do some testing. keycodes are sent from the keyboard input device for all specials keys ? (especially Fn+Fx keys) ? Thanks, -- Corentin Chary http://xf.iksaif.net -- 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
