lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 5 Oct 2011 12:59:40 -0700 (PDT)
From:	Alex Davis <alex14641@...oo.com>
To:	Keith Packard <keithp@...thp.com>,
	"terraluna977@...il.com" <terraluna977@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg@...hat.com>
Subject: Re:  Regression: i915 blank issue on kernel 3.1.0-rc3

.From: Keith Packard <keithp@...thp.com>
>> The following patch fixed my backlight issues:
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
>> index a9e0c7b..6f56676 100644
>> --- a/drivers/gpu/drm/i915/intel_panel.c
>> +++ b/drivers/gpu/drm/i915/intel_panel.c
>> @@ -262,8 +262,6 @@ void intel_panel_disable_backlight(struct drm_device *dev)
>>          dev_priv->backlight_level = intel_panel_get_backlight(dev);
>>          dev_priv->backlight_enabled = false;
>>      }
>> -
>> -    intel_panel_set_backlight(dev, 0);
>>  }
>>  
>>  void intel_panel_enable_backlight(struct drm_device *dev)
>> 
>> I've been using it since yesterday morning with no issues.
>
>Matthew -- if we cannot resolve this backlight issue, we're going to
>need to disable the new backlight code for 3.1. Do you want to try and
>fix it? Or should we bail for now?

By 'disable', do you mean revert? If so, I would the like chance to submit a patch that adds a boot parameter 
for the driver to disable the backlight by default, e.g: i915_disable_bl. Once the issues are sorted, the
parameter could be removed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ