From: Alexey Starikovskiy <aystarik@gmail.com>
To: "Jonathan S. Shapiro" <shap@eros-os.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Bug (?) in ACPI info reporting
Date: Tue, 30 Sep 2008 00:04:46 +0400 [thread overview]
Message-ID: <48E134DE.7060308@gmail.com> (raw)
In-Reply-To: <1222718070.15685.0.camel@shaptop.om-md.eros-os.com>
Jonathan S. Shapiro wrote:
> On Mon, 2008-09-29 at 23:23 +0400, Alexey Starikovskiy wrote:
>
>> Then this is most probably shortcoming of BIOS on your machine,
>> design values are hardcoded, while actual values are read from battery
>> itself.
>>
>
> That would make a sad sort of sense, yes.
>
> acpidump as attachment this time, just to confirm.
>
Ok, only two batteries are known to BIOS, one is NiMH, the other is Li-Ion.
Li-Ion has hard-coded design capacity of 0x1770 or 6000.
So, this is bug in BIOS of your machine, you might call technical
support if you care.
I am not aware of any actual use of design values, so you are pretty
safe while ignoring them.
If (^^PCI0.LPCB.EC0.MBNH)
{
Store (0x2328, Index (PBIF, One))
Store (0x1C20, Index (PBIF, 0x04))
Store ("OANI$", Index (PBIF, 0x09))
Store ("NiMH", Index (PBIF, 0x0B))
}
Else
{
Store (0x1770, Index (PBIF, One))
^^^^^^
Store (0x39D0, Index (PBIF, 0x04))
Sleep (0x32)
Store ("LION", Index (PBIF, 0x0B))
}
Regards,
Alex.
prev parent reply other threads:[~2008-09-29 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 17:08 Bug (?) in ACPI info reporting Jonathan S. Shapiro
2008-09-29 18:46 ` Alexey Starikovskiy
[not found] ` <1222714691.3688.32.camel@shaptop.om-md.eros-os.com>
2008-09-29 19:23 ` Alexey Starikovskiy
[not found] ` <1222718070.15685.0.camel@shaptop.om-md.eros-os.com>
2008-09-29 20:04 ` Alexey Starikovskiy [this message]
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=48E134DE.7060308@gmail.com \
--to=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=shap@eros-os.com \
/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).