Hi! > >>example 1: a laptop screen > >> > >>mode capacity power description > >>0 0 0 off > >>1 100 100 full brightness > >>2 70 60 half power to the backlight > >>3 50 35 quarter power to the backlight > >>4 30 25 eighth power to the backlight > >>5 5 10 backlight off. > >> > >>example 2: a front-panel display on a server (no > >>variable backlight > >>control) > >> > >>mode capacity power description > >>0 0 0 off > >>1 100 100 backlight on > >>2 50 10 backlight off > > > > > >the problem is: the person who SETS these needs to know > >what they mean. > > that's what the description is for. this info can be > provided by the driver as part of the list_modes() > function.
That's what /sys/class/backlight/ is for :-). > >as someone who wrote (part of) a power policy manager; > >sorry but you > >take away information I need, and in addition the > >different API's are > >absolutely no big deal. > > assuming that nobody else chimes in to disagree with you > I'll accept your judgement and drop the issue. Just for the record, I agree with Arjan here. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
