Hi! > > As for the modeling how the hotkey controls the LED as a trigger, > > although I do like this from one pov, I can see Jacek's point that > > this is confusing as there really is nothing to configure here, > > where as normally a user could do "echo none > trigger" to break > > the link. So I think that is best (cleanest /minimal non confusing > > API) with just the hw_brightness_change sysfs-attribute and not > > model this as a trigger. > > I can accept with this solution (no trigger, event on new sysfs file > which returns current/actual brightness state, new sysfs file only for > devices which can report brightness state). > > But I'm not sure if it is really fixing that original problem with high > power usage... Yes, it is fixing that problem. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
------------------------------------------------------------------------------
_______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
