On Sat, Nov 23, 2013 at 10:40:15PM -0200, Henrique de Moraes Holschuh wrote: > On Fri, 22 Nov 2013, Matthew Garrett wrote: > > We have userspace that relies on uevents of type > > BACKLIGHT_UPDATE_HOTKEY. I don't know that we have userspace that relies > > on uevents of type BACKLIGHT_UPDATE_SYSFS. > > Any OSD application would have to rely on both uevent types, or it is broken > (and to test that, just write a level to sysfs and watch the OSD app fail to > tell you about the backlight level change...) Right, OSDs are supposed to respond to keypresses, not arbitrary changes of backlight. If the user's just echoed 8 into brightness, they know they set the brightness to 8 - they don't need an OSD to tell them that. BACKLIGHT_UPDATE_HOTKEY is when the firmware itself has changed the brightness in response to a keypress, and so reporting the keypress would result in additional backlight changes. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel