From: Berthold Cogel <cogel@rrz.uni-koeln.de>
To: linux-acpi@vger.kernel.org
Cc: Johan Vromans <jvromans@squirrel.nl>
Subject: Re: Was: Re: UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI
Date: Sat, 22 Apr 2006 20:02:45 +0200 [thread overview]
Message-ID: <444A6FC5.7050705@rrz.uni-koeln.de> (raw)
In-Reply-To: <m2k69ji8c2.fsf@phoenix.squirrel.nl>
Johan Vromans wrote:
> 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.
I would appreciate this. I'm using this patch for my kernels. But there
seems to be a problem with the latest ACPI patches with at least kernel
2.6.16.9, which I tried yesterday.
linux-2.6.16.9
acpi-release-20060310-2.6.16.diff
acpi-dsdt-initrd-v0.8.1-2.6.16.patch
make bzImage
....
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `acpi_find_dsdt_initrd':
(.text+0x2526d): undefined reference to `ACPI_MEM_ALLOCATE'
drivers/built-in.o: In function `acpi_find_dsdt_initrd':
(.text+0x252c8): undefined reference to `ACPI_MEM_FREE'
drivers/built-in.o: In function `acpi_tb_get_table_body':
(.text+0x3772e): undefined reference to `ACPI_MEM_FREE'
make: *** [.tmp_vmlinux1] Fehler 1
Building the kernel with the ACPI patches or with the initrd patch
works. But the combination .....
Seems that something has been changed in the ACPI patches.
> 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
This was what I used in the first time with kernel 2.6.11 when I got my
notebook.
> 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.)
I haven't been much of a software developer myself and my C is rusty. I
read LKML just out of curiosity. But I'm willing to do the testing part.
Berthold
next prev parent reply other threads:[~2006-04-22 18:02 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
2006-04-22 18:02 ` Berthold Cogel [this message]
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=444A6FC5.7050705@rrz.uni-koeln.de \
--to=cogel@rrz.uni-koeln.de \
--cc=jvromans@squirrel.nl \
--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