public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH][RFC] Kill off legacy power management stuff.
Date: Wed, 18 Apr 2007 14:11:44 -0400	[thread overview]
Message-ID: <46265F60.4040600@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704172045100.18821@localhost.localdomain>

Robert P. J. Day wrote:
> On Tue, 17 Apr 2007, Bill Davidsen wrote:
>
>   
>> Rafael J. Wysocki wrote:
>>     
>>> [appropriate CCs added]
>>>
>>> On Friday, 13 April 2007 02:33, Robert P. J. Day wrote:
>>>       
>>>> just something i threw together, not in final form, but it represents
>>>> tossing the legacy PM stuff.  at the moment, the menuconfig entry for
>>>> PM_LEGACY lists it as "DEPRECATED", while the help screen calls it
>>>> "obsolete."  that's a good sign that it's getting close to the time
>>>> for it to go, and the removal is fairly straightforward, but there's
>>>> no mention of its removal in the feature removal schedule file.
>>>>         
>>> It's been like this for a long long time.  I think you're right that it can
>>> be
>>> dropped, but I don't know the details (eg. why it hasn't been dropped yet).
>>>
>>>       
>> One reason was that there are (were?) a number of machines which only powered
>> down properly using apm. It was discussed as part of shutting down after power
>> failure when your UPS is running out of power.
>>     
>
> um ... what does APM have to do with legacy PM?  two different issues,
> no?
>   
Since the patches are going into apm.c and apm was used for suspend and 
poweroff before ACPI was a feature of the hardware, I assume there's a 
relationship. As of 2.6.9 ACPI still couldn't power down one of my old 
boxes, it hasn't been updated since that time, so I can't say what later 
kernels will do.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

  reply	other threads:[~2007-04-18 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0704122025380.3628@CPE00045a9c397f-CM001225dbafb6>
2007-04-13  8:22 ` [PATCH][RFC] Kill off legacy power management stuff Rafael J. Wysocki
2007-04-13  9:51   ` David Brownell
2007-04-15 10:23   ` Pavel Machek
2007-04-17 22:12   ` Bill Davidsen
2007-04-17 22:28     ` David Brownell
2007-04-18  0:46     ` Robert P. J. Day
2007-04-18 18:11       ` Bill Davidsen [this message]
2007-04-18 18:31         ` Robert P. J. Day
2007-04-18 20:10         ` Pavel Machek

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=46265F60.4040600@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rpjday@mindspring.com \
    /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