From: Ferenc Wagner <wferi@niif.hu>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: linux-acpi@vger.kernel.org, "Rafael J.Wysocki" <rjw@sisk.pl>
Subject: Re: reverted battery current conversion fix
Date: Tue, 16 Dec 2008 11:40:11 +0100 [thread overview]
Message-ID: <87tz94h08k.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <49476A1B.7020107@suse.de> (Alexey Starikovskiy's message of "Tue, 16 Dec 2008 11:43:07 +0300")
Alexey Starikovskiy <astarikovskiy@suse.de> 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.
next prev parent reply other threads:[~2008-12-16 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zlixxaht.fsf@szonett.ki.iif.hu>
2008-12-16 8:43 ` reverted battery current conversion fix Alexey Starikovskiy
2008-12-16 10:40 ` Ferenc Wagner [this message]
2008-12-16 10:47 ` Alexey Starikovskiy
2008-12-16 11:39 ` Ferenc Wagner
2008-12-16 14:28 ` Henrique de Moraes Holschuh
2008-12-16 15:06 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tz94h08k.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=astarikovskiy@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox