Hi,
On 05/19/2014 01:24 AM, Mattia Dongili wrote:
On Fri, May 16, 2014 at 10:06:15AM +0200, Hans de Goede wrote:
snip
This is only a problem with crazy PC's which have multiple firmware
API's (both standardized and custom ACPI) to control the backlight, which
also are sometimes all broken.
On Fri, May 16, 2014 at 10:06:15AM +0200, Hans de Goede wrote:
Hi,
On 05/16/2014 12:29 AM, Mattia Dongili wrote:
On Thu, May 15, 2014 at 11:04:50AM +0200, Hans de Goede wrote:
Hi All,
There are various issues with how the linux kernel currently select which
firmware backlight control
Hi,
On 05/16/2014 12:29 AM, Mattia Dongili wrote:
On Thu, May 15, 2014 at 11:04:50AM +0200, Hans de Goede wrote:
Hi All,
There are various issues with how the linux kernel currently select which
firmware backlight control (*) method to use:
1) There are various module loading ordering
On 05/16/2014 04:06 PM, Hans de Goede wrote:
Hi,
On 05/16/2014 12:29 AM, Mattia Dongili wrote:
On Thu, May 15, 2014 at 11:04:50AM +0200, Hans de Goede wrote:
Hi All,
There are various issues with how the linux kernel currently select which
firmware backlight control (*) method to use:
Hi All,
There are various issues with how the linux kernel currently select which
firmware backlight control (*) method to use:
1) There are various module loading ordering issues, leading to different
behavior depending on module load ordering:
*
On Thu, May 15, 2014 at 11:04:50AM +0200, Hans de Goede wrote:
Hi All,
There are various issues with how the linux kernel currently select which
firmware backlight control (*) method to use:
1) There are various module loading ordering issues, leading to different
behavior depending on
