linux-kernel - Re: no backlight on radeon after recent kernel "upgrade"s

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1172138450.5837.34.camel@localhost.localdomain>
Date:	Thu, 22 Feb 2007 10:00:50 +0000
From:	Richard Purdie <rpurdie@...ys.net>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Alex Romosan <romosan@...orax.lbl.gov>,
	Yaroslav Halchenko <kernel@...russian.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	linux-fbdev-devel@...ts.sourceforge.net,
	James Simmons <jsimmons@...radead.org>
Subject: Re: no backlight on radeon after recent kernel "upgrade"s

On Wed, 2007-02-21 at 23:10 -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 21 Feb 2007, Henrique de Moraes Holschuh wrote:
> > > * 'cat brightness' != 'cat actual_brightness' upon bootup (doesn't have
> > 
> > Hmm, I see this in 2.6.20 too.  And brightness is the one that is buggy.  I
> > will look into it.
> 
> Now, that was trivial to fix, and I will reply with a patch (which will have
> Cc's trimmed to just the MLs and Richard).
> 
> But really, should not the backlight *class* be doing the initial update of
> the brightness?  Looks like something that every device would need to do if
> the class doesn't do it, and unlike the "power it off on unregister" thing,
> I can't think of a reason not to do it for every backlight class device.
> 
> Please ACK the ibm-acpi patch in my next message if you'd like me to submit
> it to Len Brown for merging into 2.6.21, or NACK it if you'd rather do it in
> the backlight class core.

We can't change the backlight class code since some hardware can't read
from the device, only write to it. Initialisation in that case is a bit
different.

Richard



-
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/