From: John-otv8KCb+Bkdaa/9Udqfwiw@public.gmane.org
To: andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ACPI] ACPI patches updated (20030109)
Date: Thu, 23 Jan 2003 15:42:43 +0000 (GMT) [thread overview]
Message-ID: <E18bjUN-000FXY-00@probity.mcc.ac.uk> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A119-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
On 10 Jan, Grover, Andrew wrote:
..
> ACPI patches based upon the 20030109 label have been released.
I have a Toshiba 3000-400 laptop, which previously needed a ACPI table
bypass for it to detect the battery power levels, which I have been
doing up to 2.4.17..
I compiled up the standard 2.4.20 and my bypass hack didn't work
anymore..
I downloaded the 20030109 patch and tried it out with 2.4.20, but the
compilation failed in
arch/i386/kernel/mpparse.c
I replaced the offending function by the one from the previous 20021212
patch and the 2.4.20 kernel compiled OK.
The patched 2.4.20 kernel now detects the laptop battery correctly along
with lots of other goodies that I'd not seen before..
Bye for now, and keep up the good work..
John
next prev parent reply other threads:[~2003-01-23 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 18:38 ACPI patches updated (20030109) Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A119-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-10 20:16 ` [ACPI] " Jurgen Kramer
2003-01-15 10:03 ` [PATCH] " Sergio Visinoni
2003-01-23 15:42 ` John-otv8KCb+Bkdaa/9Udqfwiw [this message]
[not found] ` <E18bjUN-000FXY-00-s4cbsuY0qait6LrQLftYFlpr/1R2p/CL@public.gmane.org>
2003-01-23 16:31 ` "bypass" ? Stefan Behnel
[not found] ` <3E3018DA.7000505-8NdywcgfOMlWMvVl7B+zuCEWGD4kr0XT@public.gmane.org>
2003-01-24 12:34 ` John-otv8KCb+Bkdaa/9Udqfwiw
2003-01-23 17:10 ` ACPI patches updated (20030109) Ducrot Bruno
2003-01-10 23:51 ` Andrew Walrond
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=E18bjUN-000FXY-00@probity.mcc.ac.uk \
--to=john-otv8kcb+bkdaa/9udqfwiw@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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