From: Stephen White <stephen-acpi-devel-4QvXXjU8Dv4@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Pushing ACPI to 2.4.20?
Date: Wed, 25 Sep 2002 11:07:16 +0100 [thread overview]
Message-ID: <20020925100716.GA16721@the.earth.li> (raw)
In-Reply-To: <3D90E44B.2030400-mn4gwa5WIIQysxA8WJXlww@public.gmane.org>
---- Original Message ----
> From ahaning-mn4gwa5WIIQysxA8WJXlww@public.gmane.org <ahaning@mindspring.com>
> Date: Tuesday, 24 Sep 2002, 23:16
>
> Perhaps I'm misunderstanding something or I just do not know what I'm
> doing WRT ACPI on my machine. I don't understand why there would be any
> push to get ACPI in the mainstream kernel when it seems that the major
> goal for now is just booting and assigning IRQs.
There are various reasons for this:
* Power management. Some modern laptops do not support apm - they don't
idle properly, monitor temperature and turn their fan on and off, report
battery status, throttle the CPU or switch off unless you use ACPI.
* To provide a basis for patches such as swsusp that provides
suspend-to-disk, and for projects such as those working to support
speedstep.
* IIRC some architectures require ACPI to assign IRQs to boot properly.
It is also predominantly the same code that is used in the 2.5.x kernels
where suspend-to-RAM and suspend-to-disk are supported and given the
above bullet points it is worth making as much as possible of this
functionality available to 2.4.x users.
The first point is probably the most crucial. If you have one of many
modern laptops and want to be able to use it for purposes other than
frying eggs and seeing quite how quickly it is possible to drain a
battery but don't want to brave 2.5.x then you're left with no choice
but 2.4.x+ACPI patchs.
I dare say there are other reasons I've missed here.
--
Stephen White <stephen-acpi-devel-4QvXXjU8Dv4@public.gmane.org>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-09-25 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 22:16 Pushing ACPI to 2.4.20? ahaning-mn4gwa5WIIQysxA8WJXlww
[not found] ` <3D90E44B.2030400-mn4gwa5WIIQysxA8WJXlww@public.gmane.org>
2002-09-25 10:07 ` Stephen White [this message]
2002-09-25 11:37 ` Matthew Wilcox
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=20020925100716.GA16721@the.earth.li \
--to=stephen-acpi-devel-4qvxxju8dv4@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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