From: Johan Vromans <jvromans@squirrel.nl>
To: Berthold Cogel <cogel@rrz.uni-koeln.de>
Cc: Johan Vromans <jvromans@squirrel.nl>, linux-acpi@vger.kernel.org
Subject: Re: Was: Re: UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI
Date: Fri, 21 Apr 2006 11:30:53 +0200 [thread overview]
Message-ID: <m2k69ji8c2.fsf@phoenix.squirrel.nl> (raw)
In-Reply-To: <44480F0B.5020106@rrz.uni-koeln.de> (Berthold Cogel's message of "Fri, 21 Apr 2006 00:45:31 +0200")
Berthold Cogel <cogel@rrz.uni-koeln.de> writes:
> Johan Vromans wrote:
>> https://sourceforge.net/project/showfiles.php?group_id=129330
>
> Thanks! I've overlooked the patches at Sourceforge.
> Is there any chance to get the patch into the kernel somehow?
There are two patches required. One patch is to allow a
custom-supplied DSDT in initrd. This is a harmless patch that would be
very nice to have in the kernel, and the feature could even be enabled
by default[1]. Several distro's already do this.
The other patch (I'm replying for Rich now, so don't point _me_ down
on the deeper details) concerns the use of a semaphore instead of spin
lock in ec. This is to overcome loss of interrupts while reading out
the bus. There has been much debate about this patch, and it can be
argued that it implements the right solution. (It does the job,
though.)
But the best solution would be to have a kernel module that deals with
this kind of smart batttery subsystems, and provide the correct
information for userland (hal?) to react upon. This is basically the
original approach taken by Pedro Venda, Bruno Ducrot and completed for
2.6.10 (or so) by Rich Townsend[2]. Unfortunately, recent changes to
the i2c drivers conflict with the changes required for this approach,
and I haven't been able to find out how to modify the patches for the
2.6.16 kernel. (Help appreciated.)
-- Johan
[1] For my Acer Travelmate 4001WLMi I need to supply a custom DSDT
anyway, since some of the original DSDT data is just wrong...
[2] http://shayol.bartol.udel.edu/~rhdt/download/acpi_sbs-20050120.tar.gz
next prev parent reply other threads:[~2006-04-21 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 20:27 UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI Brown, Len
2006-01-27 11:43 ` Johan Vromans
2006-04-19 23:31 ` Was: " Berthold Cogel
2006-04-20 10:43 ` Johan Vromans
2006-04-20 11:32 ` Matthew Garrett
2006-04-22 20:53 ` Johan Vromans
2006-04-22 21:23 ` Matthew Garrett
2006-04-20 22:45 ` Berthold Cogel
2006-04-21 9:30 ` Johan Vromans [this message]
2006-04-22 18:02 ` Berthold Cogel
2006-04-22 18:27 ` Johan Vromans
2006-04-23 21:56 ` Berthold Cogel
2006-04-24 9:36 ` Johan Vromans
2006-05-09 23:43 ` Berthold Cogel
2006-06-01 16:29 ` Johan Vromans
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=m2k69ji8c2.fsf@phoenix.squirrel.nl \
--to=jvromans@squirrel.nl \
--cc=cogel@rrz.uni-koeln.de \
--cc=linux-acpi@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