I have done some research on this problem and come across an informative discussion on this problem on a Debian-related mailing list:
http://<email address hidden>/msg01135.html
What I got from this is:
The Eee pc's battery does not adhere to ACPI standards in reporting its capacity, returning a percentage in a field which is specified as having the unit mAh. Linux (ACPI driver, I guess) exports the percentage value of capacity in mAh in /proc/acpi/battery (and possibly elsewhere), which leads into problems in anything that uses it.
So where should this be fixed? Given that this has slim chance of happening in Eee pc's BIOS and no chance of everyone even upgrading to that unlikely new BIOS version, I would say the next best place would be just one step up the ladder -- in Linux ACPI driver -- because if this would be fixed (only) in devicekit-power, other processes that don't rely on dk-p, e.g. manually cat'ing /proc/acpi/battery/BAT0/info, would still return erroneous results.
I have done some research on this problem and come across an informative discussion on this problem on a Debian-related mailing list: /msg01135. html
http://<email address hidden>
What I got from this is:
The Eee pc's battery does not adhere to ACPI standards in reporting its capacity, returning a percentage in a field which is specified as having the unit mAh. Linux (ACPI driver, I guess) exports the percentage value of capacity in mAh in /proc/acpi/battery (and possibly elsewhere), which leads into problems in anything that uses it.
So where should this be fixed? Given that this has slim chance of happening in Eee pc's BIOS and no chance of everyone even upgrading to that unlikely new BIOS version, I would say the next best place would be just one step up the ladder -- in Linux ACPI driver -- because if this would be fixed (only) in devicekit-power, other processes that don't rely on dk-p, e.g. manually cat'ing /proc/acpi/ battery/ BAT0/info, would still return erroneous results.