On Tue, 2008-12-30 at 18:37 +0800, Richard Purdie wrote: > On Wed, 2008-12-24 at 11:07 +0800, Zhang Rui wrote: > > /sys/class/backlight/.../brightness returns a cached value, > > which confuses a lot of users. > > > > Make the "brightness" reflect the actual backlight levels, > > and mark /sys/class/backlight/.../brightness as depreacated > > in this patch. > > This isn't an acceptable approach I'm afraid. We have some hardware > which needs limiting of the backlight brightness in cases of low battery we use "brightness" as the backlight limiting? then how does it work? users can always set it to a higher or lower value no matter whether it's low battery or not. IMO we'd better to use another file instead. I got a couple of bugs about "the brightness file doesn't work", because if people can change the backlight by poking "brightness", they prefer to get the current brightness by reading it. what do you think? > for example. "brightness" is the user requested value, > "actual_brightness" is the one that is actually active. why do we need the "user requested value"? does some application depend on it? thanks, rui -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
