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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
