From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG?] APM is hidden in menuconfig
Date: Thu, 21 Feb 2008 01:23:44 +0100 [thread overview]
Message-ID: <200802210123.44367.rjw@sisk.pl> (raw)
In-Reply-To: <20080220120828.GD3885@ff.dom.local>
On Wednesday, 20 of February 2008, Jarek Poplawski wrote:
> Hi,
>
> I needed APM to have poweroff on old box. So, in 2.6.24.2 menuconfig:
>
> 1) Power management options -->
> No APM.
> 2) [*] Power Management support
> No APM. I can see ACPI...
> 3) I try searching with "/" + "APM"
> APM [=n]
> Depends on: !X86_VOYAGER && X86_32 && PM_SLEEP && !X86_VISWS
> 4) I check above: all correct except:
> Symbol: PM_SLEEP [=n]
> No more "depends on".
> 5) Exit menuconfig - enter grep:
> 6) Some time wasting in arch/.
> 7) less kernel/power/Kconfig:
> config PM_SLEEP
> bool
> depends on SUSPEND || HIBERNATION
> default y
> ...
> config SUSPEND
> bool "Suspend to RAM and standby"
> depends on PM
> depends on SUSPEND_UP_POSSIBLE || SUSPEND_SMP_POSSIBLE
> default y
> ---help---
> Allow the system to enter sleep states in which main memory is
> powered and thus its contents are preserved, such as the
> suspend-to-RAM state (i.e. the ACPI S3 state).
>
> 8) Back to menuconfig:
> [*] Suspend to RAM and standby
>
> Bingo! APM revealed! (And not even "DEPRECATED"!)
>
> So, has it to be so hard? It seems not - at least in good old times...
Something in APM uses some code from drivers/base/power/main.c that depends
on PM_SLEEP.
Thanks,
Rafael
next prev parent reply other threads:[~2008-02-21 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 12:08 [BUG?] APM is hidden in menuconfig Jarek Poplawski
2008-02-21 0:23 ` Rafael J. Wysocki [this message]
[not found] ` <E1JS02I-0003gO-Py@faramir.fjphome.nl>
2008-02-21 1:21 ` Rafael J. Wysocki
2008-02-21 7:43 ` Jarek Poplawski
2008-02-21 8:23 ` Jarek Poplawski
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=200802210123.44367.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jarkao2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.