From: Alvaro Lopes <alvieboy@alvie.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI update (20030122)
Date: Fri, 24 Jan 2003 13:09:07 +0000 [thread overview]
Message-ID: <3E313AF3.60109@alvie.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A131@orsmsx401.jf.intel.com>
Grover, Andrew wrote:
>Hi all,
>
>The latest ACPI patch is now available at http://sf.net/projects/acpi .
>Non-Linux packages will be available within 24 hours from
>http://developer.intel.com/technology/iapc/acpi/downloads.htm .
>
>
Still not working properly :/
Right now with 2.4.21-pre3 keventd 'eats' all my cpu.
Perhaps same problem I got with 2.5.59 (kernel does nothing but handle
IRQ's from acpi), but at least with 2.4 it gets to boot.
--
Álvaro Lopes
---------------------
A .sig is just a .sig
next prev parent reply other threads:[~2003-01-24 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 22:44 [PATCH] ACPI update (20030122) Grover, Andrew
2003-01-24 0:00 ` Dave Jones
2003-01-24 0:10 ` Halil Demirezen
2003-01-24 2:22 ` [TRIVIAL] " Sergio Visinoni
2003-01-24 15:51 ` [ACPI] " Ducrot Bruno
2003-01-24 13:09 ` Alvaro Lopes [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 0:09 Grover, Andrew
2003-01-24 0:59 ` Dave Jones
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=3E313AF3.60109@alvie.com \
--to=alvieboy@alvie.com \
--cc=linux-kernel@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