Alexey Starikovskiy <astarikovskiy@xxxxxxx> writes: > Ferenc Wagner wrote: > >> 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. > > Currently, Rafael suggests, that it is too late to fix the kernel... Too late for 2.6.28 or too late for ever? The ACPI sysfs interface appeared about one year ago, if I read the git log right, documentation followed this spring. If the supposedly clean sysfs interface can't live up to its very precise and well thought out documentation, that should be documented at least. :( What a pity. -- Regards, 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
