On Wed, Apr 14, 2010 at 12:26 PM, Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > On Wed, Apr 14, 2010 at 12:14:04PM -0500, Chris Bagwell wrote: > >> Does the acpi-video logic not have logic on its own to send key >> events? So I guess laptops that don't have custom modules to handle >> this type of stuff don't get visual feedback from gnome-power-manager? > > It does, but it's dependent upon the firmware sending them. I think the following tells me firmware is sending them. If I leave acpi_osi="Windows 2009" so that eeepc_laptop doesn't get loaded, I see events like this on /pro/acpi/event: video LCDD 00000087 00000000 video LCDD 00000087 00000000 video LCDD 00000086 00000000 video LCDD 00000086 00000000 Thats a couple decreases followed by a couple increases. If I change acpi_osi="!Windows 2009" with and without acpi_backlight=vendor then I get events like: hotkey ATKD 00000027 00000000 hotkey ATKD 00000026 00000000 hotkey ATKD 00000025 00000000 hotkey ATKD 00000024 00000000 The main difference is that with acpi_backlight=vendor then I also get events sent on /dev/input/event*. >From here, I'd have to compile some custom eeepc-laptop's and see if bd->props.brightness is being updated with correct values and then we could do just the event send while skipping the update part. ...or is there a way to not register for events 0x20 to 0x2f and let ACPI Video process those? If later is more correct way, is it obvious why that code isn't sending key events today? Chris -- 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
