Alexey Starikovskiy <astarikovskiy@xxxxxxx> writes: > Ferenc Wagner wrote: > >> the wild values probably came from some application, which >> previously worked around the wrong sysfs current value (supposedly >> correctly interpreting it as power) and thus got broken by the fix. > > Yes, the application is kpowersaved and it is written with the > assumption that it could get remaining time by dividing either > energy_now or charge_now by current_now. So the first choice depends on the current buggy kernel behaviour. What's the plan of action in such cases? I found some notes that kpowersaved can or could use HAL for getting this information, in which case HAL also should be fixed. At least their bug tracker[1] on SF doesn't contain any such issue, maybe one should be added by somebody actually using it if the kernel is to be fixed. [1] http://sourceforge.net/tracker/?atid=700009&group_id=124576&func=browse -- Cheers, Feri. -- 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
