On Tue, 1 Feb 2011, Chris Wilson wrote:
On Tue, 1 Feb 2011 07:05:16 -0500 (EST), "Robert P. J. Day" rpjday@crashcourse.ca wrote:
any new developments on this issue?
Not really, the only thing left to confirm is whereabouts it goes wrong.
About the only routine of significance is alse_set_backlight().
Does a 'return ASLE_BACKLIGHT_FAILED;' as the first line of that function have a similar effect to the current hack?
apparently, it does:
@@ -150,6 +150,8 @@ static u32 asle_set_backlight(struct drm_device *dev, u32 bclp) struct opregion_asle *asle = dev_priv->opregion.asle; u32 max;
+return ASLE_BACKLIGHT_FAILED; // rday + if (!(bclp & ASLE_BCLP_VALID)) return ASLE_BACKLIGHT_FAILED;
gives me a good boot. this is the diff with relation to the recently tagged 2.6.38-rc3. anything else you want me to test?
rday