On 08/07/2013 03:44 PM, Borislav Petkov wrote: > On Sun, Jun 09, 2013 at 07:01:36PM -0400, Matthew Garrett wrote: >> Windows 8 introduced new policy for backlight control by pushing it out to >> graphics drivers. This appears to have coincided with a range of vendors >> adding Windows 8 checks to their backlight control code which trigger either >> awkward behaviour (Lenovo) or complete brokenness (some Dells). The simplest >> thing to do would be to just disable ACPI backlight control entirely if the >> firmware indicates Windows 8 support, but it's entirely possible that >> individual graphics drivers might still make use of the ACPI functionality in >> preference to native control. > > Maybe tangential, so Aaron and I were wondering on > https://bugzilla.kernel.org/show_bug.cgi?id=60680 whether it would make > sense to handle the backlight control strictly in the kernel, without > going to userspace and back? I think this would require the kernel has the knowledge of which backlight interface this system is using or should be using, or it wouldn't know which interface should receive and process the event... -Aaron > > Background is that on my x230, I needed to connect the > Fn-Fx backlight hotkey presses to a script to write to > /sys/class/backlight/intel_backlight/brightness because Fluxbox doesn't > do that (and maybe doesn't have to). > > So, without presuming any ACPI or backlight knowledge, can we make the > backlight control work only in the kernel by connecting the hotkey > presses to some backlight controlling interface which backlight-capable > devices implement so that it works regardless of userspace environment? > Even if the machine is not running X? > > Hmmm. > > Thanks. > _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
