From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Binary Xerroz <xerroz-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI: Battery information?
Date: Wed, 9 Jun 2004 09:54:01 +0200 [thread overview]
Message-ID: <20040609075401.GT13782@poupinou.org> (raw)
In-Reply-To: <40C6319A.7080707-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.org>
On Tue, Jun 08, 2004 at 02:37:30PM -0700, Binary Xerroz wrote:
> Included is the output of acpidmp, also i included a diff patch for
> kernel 2.6.6, patched with patch from acpi.sf.net
> About the battery.c, the main reason for my modifications is
> because to me ACPI for linux doesnt expect a battery to be removed
> (physically) such as on a laptop. the modified code reruns check
> routines to make sure the battery is still there, if not its updated as
> no present; before it still showed as present, but had critical status
> and such, this patch fixes that and updates accordingly. Double check
> routines added to make it work on status update instead of two.
> Anything else, let me know.
ACPI support hotplug of batteries if the hardware generate an SCI (an
interrupt), then a handler is called which will call an AML method which
in turn will call a special opcode (Notify()).
Then, after a Notify(FOO, 0x80) (or 0x81),
drivers/acpi/battery::acpi_battery_notify() will be called which will
reprobe the battery FOO (and (re)attach or detach to the acpi bus
if needed).
So it's more likely a trouble somewhere in your DSDT, or a bug under linux.
It may be also the case that the hardware do not support this scheme,
(the problem is that the interrupt used for this is not the same for APM
and ACPI, and hardware need to be configured of the mode of operation.
It's done at init stage of kernel).
So one step perhaps to debug this is to see if interrupts are generated.
You can, for example, do a
watch -d 'cat /proc/interrupts'
then see if the interrupt associated to acpi change whenever you
plug/unplug a battery.
btw, your acpidump.bz2 seems to be corrupted somehow. Could you please
resend it?
ps: my email client do not support HTML. Would be fine if you can send
at least a text alternative somehow.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
next prev parent reply other threads:[~2004-06-09 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 23:41 ACPI: Battery information? Binary Xerroz
[not found] ` <40C4FD27.7000805-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.org>
2004-06-08 0:47 ` Ow Mun Heng
2004-06-08 7:20 ` wwp
[not found] ` <20040608092045.72e15c4c-x0nrVmVds9QJrXWdq/lNz0B+6BGkLq7r@public.gmane.org>
2004-06-08 9:47 ` Bruno Ducrot
[not found] ` <20040608094707.GM13782-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-06-08 10:14 ` wwp
[not found] ` <20040608121424.5b559830-x0nrVmVds9QJrXWdq/lNz0B+6BGkLq7r@public.gmane.org>
2004-06-08 11:40 ` Bruno Ducrot
[not found] ` <40C58F45.2040108@users.xeroprj.org>
[not found] ` <40C58F45.2040108-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.org>
2004-06-08 11:34 ` Bruno Ducrot
[not found] ` <20040608113456.GN13782-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-06-08 21:37 ` Binary Xerroz
[not found] ` <40C6319A.7080707-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.org>
2004-06-09 7:54 ` Bruno Ducrot [this message]
[not found] ` <20040609075401.GT13782-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-06-09 9:44 ` Bruno Ducrot
2004-06-10 16:43 ` Stefan Seyfried
[not found] ` <20040610164324.GA6919-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-06-10 21:16 ` Bruno Ducrot
[not found] ` <20040610211644.GF13782-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-06-11 5:10 ` Stefan Seyfried
[not found] ` <20040611051031.GA5237-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-06-12 19:07 ` Michael Frank
2004-06-14 14:06 ` Bruno Ducrot
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=20040609075401.GT13782@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xerroz-BC6XjCpM3eF0abU8S3f8Vti2O/JbrIOy@public.gmane.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