From: Richard Hughes <hughsient@gmail.com>
To: Shem Multinymous <multinymous@gmail.com>
Cc: Xavier Bestel <xavier.bestel@free.fr>,
Jean Delvare <khali@linux-fr.org>,
davidz@redhat.com, David Woodhouse <dwmw2@infradead.org>,
Dan Williams <dcbw@redhat.com>,
linux-kernel@vger.kernel.org, devel@laptop.org,
sfr@canb.auug.org.au, len.brown@intel.com, greg@kroah.com,
benh@kernel.crashing.org,
linux-thinkpad mailing list <linux-thinkpad@linux-thinkpad.org>,
Pavel Machek <pavel@suse.cz>
Subject: Re: [PATCH v2] Re: Battery class driver.
Date: Wed, 01 Nov 2006 13:26:17 +0000 [thread overview]
Message-ID: <1162387577.5001.7.camel@hughsie-laptop> (raw)
In-Reply-To: <41840b750610310606t2b21d277k724f868cb296d17f@mail.gmail.com>
On Tue, 2006-10-31 at 16:06 +0200, Shem Multinymous wrote:
>
> In the case at hand we have mWh and mAh, which measure different
> physical quantities. You can't convert between them unless you have
> intimate knowledge of the battery's chemistry and condition, which we
> don't.
I'm thinking specifically for ACPI at the moment.
When ACPI can't work out a value, i.e. it's not known, it returns a
value of 0xFFFFFFFF. This can happen either for a split second on
disconnect, or if the hardware really doesn't know the value.
With the battery class driver, how would that be conveyed? Would the
sysfs file be deleted in this case, or would the value of the sysfs key
be something like "<invalid>".
This is something I'm just thinking about for the HAL backend, and
whatever is decided should probably be documented.
Richard.
next prev parent reply other threads:[~2006-11-01 13:41 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1161628327.19446.391.camel@pmac.infradead.org>
2006-10-23 19:18 ` Dan Williams
2006-10-23 19:58 ` Richard Hughes
2006-10-23 20:10 ` Roland Dreier
2006-10-23 20:48 ` David Woodhouse
2006-10-24 3:44 ` Benjamin Herrenschmidt
2006-10-24 17:18 ` Richard Hughes
2006-10-25 7:42 ` [PATCH v2] " David Woodhouse
2006-10-25 9:54 ` Shem Multinymous
2006-10-25 12:11 ` David Woodhouse
2006-10-25 14:42 ` Shem Multinymous
2006-10-25 22:25 ` David Woodhouse
2006-10-25 23:39 ` Shem Multinymous
2006-10-28 12:15 ` David Woodhouse
2006-10-28 13:22 ` Richard Hughes
2006-10-28 14:34 ` Shem Multinymous
2006-10-28 14:36 ` David Woodhouse
2006-10-28 14:55 ` David Zeuthen
2006-10-28 18:52 ` Pavel Machek
2006-10-28 19:48 ` David Zeuthen
2006-10-28 21:10 ` Pavel Machek
2006-10-28 15:09 ` David Zeuthen
2006-10-28 15:31 ` David Zeuthen
2006-10-28 18:12 ` Shem Multinymous
2006-10-31 7:49 ` Greg KH
2006-10-31 13:28 ` Shem Multinymous
2006-11-01 19:31 ` Greg KH
2006-11-01 19:53 ` Shem Multinymous
2006-11-01 20:53 ` Greg KH
2006-11-01 23:55 ` [ltp] " Henrique de Moraes Holschuh
2006-11-02 3:45 ` Greg KH
2006-11-02 17:49 ` Bill Davidsen
2006-11-02 19:19 ` Richard Hughes
2006-11-02 21:20 ` Pavel Machek
2006-11-03 12:46 ` Henrique de Moraes Holschuh
2006-11-03 15:13 ` Stefan Seyfried
2006-11-02 22:01 ` Pavel Machek
2006-11-03 13:12 ` U Kuehn
2006-11-05 20:52 ` Pavel Machek
2006-11-05 21:02 ` Jean Delvare
2006-11-01 21:27 ` Pavel Machek
2006-11-01 21:32 ` Richard Hughes
2006-10-31 7:59 ` Jean Delvare
2006-10-31 13:42 ` Shem Multinymous
2006-10-31 13:51 ` Xavier Bestel
2006-10-31 14:06 ` Shem Multinymous
2006-11-01 13:26 ` Richard Hughes [this message]
2006-11-01 13:54 ` David Woodhouse
2006-11-01 14:36 ` Henrique de Moraes Holschuh
2006-11-01 16:36 ` Shem Multinymous
2006-11-01 16:55 ` Henrique de Moraes Holschuh
2006-11-01 19:30 ` Greg KH
2006-11-02 7:52 ` Jean Delvare
2006-11-02 8:39 ` Richard Hughes
2006-11-02 13:54 ` Henrique de Moraes Holschuh
2006-11-02 17:52 ` Bill Davidsen
2006-11-02 19:26 ` Richard B. Johnson
2006-11-03 13:23 ` Henrique de Moraes Holschuh
2006-11-03 14:20 ` Richard B. Johnson
2006-11-03 16:10 ` [ltp] " Henrique de Moraes Holschuh
2006-10-28 18:55 ` Pavel Machek
2006-10-28 19:53 ` David Zeuthen
2006-10-28 21:05 ` Pavel Machek
2006-10-28 21:54 ` Henrique de Moraes Holschuh
2006-10-26 9:55 ` [ltp] " FeRD
2006-10-28 5:12 ` Pavel Machek
2006-10-24 3:41 ` Benjamin Herrenschmidt
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=1162387577.5001.7.camel@hughsie-laptop \
--to=hughsient@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=davidz@redhat.com \
--cc=dcbw@redhat.com \
--cc=devel@laptop.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-thinkpad@linux-thinkpad.org \
--cc=multinymous@gmail.com \
--cc=pavel@suse.cz \
--cc=sfr@canb.auug.org.au \
--cc=xavier.bestel@free.fr \
/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
Powered by JetHome