mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Len Brown <lenb@kernel.org>
Cc: davej@codemonkey.org.uk, Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Kill off legacy power management stuff.
Date: Wed, 18 Apr 2007 19:45:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704181940260.5400@localhost.localdomain> (raw)
In-Reply-To: <200704181723.16241.lenb@kernel.org>

On Wed, 18 Apr 2007, Len Brown wrote:

> On Wednesday 18 April 2007 16:23, Robert P. J. Day wrote:

> > ok, i get it now and -- correct me if i'm wrong -- all my legacy PM
> > removal patch was doing was exposing a design boo-boo in which
> > APM/ACPI contention was being handled by a macro in a subsystem even
> > older than either of them, right?
>
> yeah, it didn't start out that way, the bug was added when the
> CONFIG_PM_LEGACY #define was added.
>
> > so all that needs to be done is add back in a contention solution
> > of some kind that doesn't rely on that ancient system, yes?
>
> Yes, it is a matter of making the variable not go away when the
> #define goes away.
>
> > as for that thinkpad t30 situation, well, that's just borked, and
> > should be fixed.
>
> yes, the actual failure is that APM mode on the T30 hangs -- and
> that is independent of the issue at hand.  However, there could be
> other failures on other machines when both APM and ACPI think they
> are active.

at this point, i think the proper approach is to locate and remove all
dependencies on the legacy PM code, which includes making sure there's
a reliable contention mechanism for APM and ACPI that doesn't need
anything out of the legacy code or header files.  once that's done,
the legacy deletion itself should be trivial.

the obvious place for the contention stuff is, i would think,
include/linux/pm.h, yes?

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  0:33 Robert P. J. Day
2007-04-13  8:09 ` Stephen Rothwell
2007-04-13  8:20   ` Robert P. J. Day
2007-04-13  8:30     ` Stephen Rothwell
2007-04-13  8:50       ` Robert P. J. Day
2007-04-14 12:22       ` {Spam?} " Robert P. J. Day
2007-04-14 13:01       ` Robert P. J. Day
2007-04-18 19:24         ` Len Brown
2007-04-18 20:23           ` Robert P. J. Day
2007-04-18 21:23             ` Len Brown
2007-04-18 23:45               ` Robert P. J. Day [this message]
2007-04-18 23:58               ` Dave Jones
2007-04-19  0:35                 ` Robert P. J. Day
2007-04-19 17:27                   ` Len Brown
2007-04-13  8:22 ` Rafael J. Wysocki
2007-04-13  9:51   ` [linux-pm] " David Brownell
2007-04-15 10:23   ` Pavel Machek
2007-04-17 22:12   ` Bill Davidsen
2007-04-17 22:28     ` [linux-pm] " David Brownell
2007-04-18  0:46     ` Robert P. J. Day
2007-04-18 18:11       ` Bill Davidsen
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=Pine.LNX.4.64.0704181940260.5400@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=davej@codemonkey.org.uk \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®