linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mochel <mochel@osdl.org>
To: Sean Middleditch <smiddle@twp.ypsilanti.mi.us>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: APM/ACPI
Date: Fri, 2 Nov 2001 10:42:42 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111021039130.15166-100000@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <1004725879.4921.36.camel@smiddle>


On 2 Nov 2001, Sean Middleditch wrote:

> Hmm, not to point fingers or anything, but...
>
> "The WindowsXP that came preinstalled supported it!"

Windows XP requires systems to be fully ACPI (1.0b?) compliant. So, you
probably have an ACPII BIOS, though many BIOSes have some remnants of APM
left in them...

> I dunno, perhaps there is some proprietary protocol?  Is ACPI backwards
> compat with APM?  I mean, if the laptop doesn't support APM, would that
> mean it can't support ACPI?

Probably not, no, and no. ACPI support in Linux is still maturing, and
many things still do not work. I would recommend the ACPI mailing list and
archives for more assistance:

	http://phobos.fs.tum.de/acpi/index.html


	-pat



  parent reply	other threads:[~2001-11-02 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 18:23 APM/ACPI Sean Middleditch
2001-11-02 18:34 ` APM/ACPI Alan Cox
2001-11-02 18:31   ` APM/ACPI Sean Middleditch
2001-11-02 18:42     ` APM/ACPI Alan Cox
2001-11-02 18:41       ` APM/ACPI Sean Middleditch
2001-11-02 18:50         ` APM/ACPI Alan Cox
2001-11-05  2:49           ` APM/ACPI Sean Middleditch
2001-11-05  8:49             ` APM/ACPI Alan Cox
2001-11-05 21:34           ` APM/ACPI Mike Panetta
2001-11-02 18:42     ` Patrick Mochel [this message]
2001-11-02 18:56       ` APM/ACPI Sean Middleditch
2001-11-05  4:06 APM/ACPI Grover, Andrew
2001-11-05 13:28 ` APM/ACPI Sean Middleditch

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.33.0111021039130.15166-100000@osdlab.pdx.osdl.net \
    --to=mochel@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smiddle@twp.ypsilanti.mi.us \
    /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;
as well as URLs for NNTP newsgroup(s).