public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Jos Hulzink <josh@stack.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.45 build failed with ACPI turned on
Date: Wed, 06 Nov 2002 15:08:42 +0000	[thread overview]
Message-ID: <26783.1036595322@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1021105193510.20035F-100000@gatekeeper.tmr.com>


davidsen@tmr.com said:
>  More to the point, define CONFIG_PM as ( CONFIG_APM | CONFIG_ACPI )
> and be able to easily handle any new PM method on whatever hardware.
> PM is not limited to Intel hardware. Make a new HAS_PM if reusing
> CONFIG_PM creates problems.

Er, there's no reason why PM even on Intel hardware should be restricted to
ACPI and APM. With appropriate chipset documentation there's nothing to stop
people from writing proper driver code to enter sleep states, etc. for i386 
chipsets just as we have for other architectures.

--
dwmw2



  reply	other threads:[~2002-11-06 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 19:37 2.5.45 build failed with ACPI turned on Grover, Andrew
2002-11-01 19:47 ` Dave Jones
2002-11-01 21:21   ` Jos Hulzink
2002-11-01 20:31     ` Dave Jones
2002-11-02 20:11       ` Jos Hulzink
2002-11-06  0:38         ` Bill Davidsen
2002-11-06 15:08           ` David Woodhouse [this message]
2002-11-06 16:33             ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 19:45 Robert Varga
2002-11-01 19:02 ` Jos Hulzink
2002-11-01 19:12 ` Jos Hulzink

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=26783.1036595322@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=davidsen@tmr.com \
    --cc=josh@stack.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox