From: Tony Vroon <tony@linx.net>
To: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Low-Level and Long-Term Battery Control
Date: Tue, 13 Apr 2010 14:24:42 +0100 [thread overview]
Message-ID: <1271165082.3529.44.camel@localhost> (raw)
In-Reply-To: <w2r45cc95261004130535y80da503ev5389bb4a97bdd58f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On Tue, 2010-04-13 at 14:35 +0200, Mohamed Ikbel Boulabiar wrote:
> I ask if the kernel can do such control without the user intention and
> in an automatic way.
Battery charge control is generally a function of the system firmware,
not of the operating system. You might be able to disassemble your DSDT
to see if there is any control of the overall charging schema.
Most firmware does not expose this though.
> Some BIOS provide to the user to select whether to block the battery
> I am not sure for the MacBook side, but it seems they don't suffer
> from such problem in the same degree as other laptop users.
It sounds like those MacBook machines have well-written firmware in that
case, at least where the charging of batteries is concerned.
> I think it is a serious problem because if you keep you battery on
> power for one week you will detect it becomes holding only 50% of its
> energy compared to when first bought.
I would suggest contacting the manufacturer, overcharging of certain
battery chemistries can be a safety hazard. If the machine is in
warranty, it sounds like time for an RMA.
> Thanks,
> Mohamed-Ikbel BOULABIAR
Regards,
--
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-13 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 12:35 Low-Level and Long-Term Battery Control Mohamed Ikbel Boulabiar
2010-04-13 13:24 ` Tony Vroon [this message]
2010-04-19 4:31 ` Andy Lutomirski
2010-04-20 13:37 ` Pavel Machek
[not found] <h2i45cc95261004120628kb38aabecr2552668f9e60d7c5@mail.gmail.com>
[not found] ` <20100415180200.GA1443@ucw.cz>
[not found] ` <q2p72dbd3151004151642p9c0b8a14yc9de251b134aec08@mail.gmail.com>
[not found] ` <20100416041509.GB1552@elf.ucw.cz>
2010-04-22 9:25 ` Mohamed Ikbel Boulabiar
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=1271165082.3529.44.camel@localhost \
--to=tony@linx.net \
--cc=boulabiar@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).