public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh@stack.nl>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	Robert Varga <nite@hq.alert.sk>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.45 build failed with ACPI turned on
Date: Sat, 2 Nov 2002 21:11:25 +0100	[thread overview]
Message-ID: <200211022111.25198.josh@stack.nl> (raw)
In-Reply-To: <20021101203121.GB2329@suse.de>

On Friday 01 November 2002 21:31, Dave Jones wrote:
> On Fri, Nov 01, 2002 at 10:21:56PM +0100, Jos Hulzink wrote:
>  > Other issue: Are ACPI and APM not mutually exclusive ? If so, I would
>  > propose a selection box: <ACPI> <APM> <none> with related options shown
>  > below. Hmzz.. there the issue of the fact that ACPI is more than power
>  > management shows up again.
>
> Whilst they can't both run at the same time, it's perfectly possible
> (and useful) to build a kernel with both included. ACPI will quit
> if APM is already running, so booting with apm=off turns the same
> kernel into 'ACPI mode'

Hmzz.. in that case I vote for dropping CONFIG_PM in favour of CONFIG_APM || CONFIG_ACPI, even though it requires some more typing for the programmers. (I'm no ACPI programmer, so I don't care ;-)

Jos


  reply	other threads:[~2002-11-02 19:04 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 [this message]
2002-11-06  0:38         ` Bill Davidsen
2002-11-06 15:08           ` David Woodhouse
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=200211022111.25198.josh@stack.nl \
    --to=josh@stack.nl \
    --cc=andrew.grover@intel.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nite@hq.alert.sk \
    /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