public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ian Soboroff <ian.soboroff@nist.gov>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Post-halloween doc updates.
Date: Fri, 31 Oct 2003 16:14:50 +0000	[thread overview]
Message-ID: <20031031161450.G4556@flint.arm.linux.org.uk> (raw)
In-Reply-To: <9cfn0bhjswn.fsf@rogue.ncsl.nist.gov>; from ian.soboroff@nist.gov on Fri, Oct 31, 2003 at 11:03:52AM -0500

On Fri, Oct 31, 2003 at 11:03:52AM -0500, Ian Soboroff wrote:
> Well, ok, but the alternatives are ACPI, which has always been spotty,

Wrong - there are systems out there which do not support ACPI (or maybe
the kernel doesn't support the ACPI which is implemented in them.)

> and two competing power management schemes from Patrick and Pavel,
> neither of which seem to actually work yet.  Wouldn't it be nice to
> have at least one working method of putting a laptop to sleep?

Indeed.  With 2.6 there are zero ways I can make my x86 laptop
suspend or hibernate.

> Once I get some free time (maybe next week, who knows) I'll try
> backing out bits of the -test8 patch to see what broke.  In the
> meantime, -test7 works great.

Oh, my problem goes back many kernel versions.  It's nothing new.
Somewhere during 2.5 development (current thinking is somewhere
around 2.5.3x) something changed which makes the APM BIOS believe
that the machine isn't in the correct state to suspend.

However, exactly what that is seems to be impossible to track down.
Building a kernel minimal driver support results in a system which
can't suspend... and by "minimal" that includes dropping stuff like
the input layer and console completely from the kernel.

It basically comes down to some really subtle change in what 2.6 is
does differently from 2.4.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2003-10-31 16:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 14:15 Post-halloween doc updates Dave Jones
2003-10-30 15:05 ` Jeff Garzik
2003-10-30 15:18   ` Dave Jones
2003-10-30 16:55     ` John Bradford
2003-10-30 15:15 ` Holger Schurig
2003-10-30 15:19   ` Dave Jones
2003-10-30 16:52 ` Randy.Dunlap
2003-10-30 17:27   ` Chris Wright
2003-10-30 18:38   ` Dave Jones
2003-10-30 18:44     ` Randy.Dunlap
2003-10-30 18:53       ` Dave Jones
2003-10-30 17:01 ` Geert Uytterhoeven
2003-10-30 19:08 ` Philipp Matthias Hahn
2003-10-30 22:16 ` bd
2003-10-31  1:32   ` Gene Heskett
2003-10-31 12:50   ` Thierry Vignaud
2003-10-30 23:11 ` Felipe Alfaro Solana
2003-10-31  0:16   ` Dave Jones
2003-10-31  2:14     ` John Levon
2003-10-31  2:30       ` Dave Jones
2003-10-31  7:34 ` ide-scsi is working [was: Post-halloween doc updates.] Nuno Silva
2003-10-31 13:42   ` Bartlomiej Zolnierkiewicz
2003-10-31 12:25 ` Post-halloween doc updates Andreas Jellinghaus
2003-10-31 15:35   ` Paul Dickson
2003-10-31 15:06 ` Ian Soboroff
2003-10-31 15:24   ` Russell King
2003-10-31 16:00     ` Aristeu Sergio Rozanski Filho
2003-10-31 16:03     ` Ian Soboroff
2003-10-31 16:14       ` Russell King [this message]
2003-10-31 17:56       ` Michael Clark
2003-11-10 23:43       ` bill davidsen
2003-11-11  1:09         ` Rob Landley
2003-11-10 14:11     ` Pavel Machek
2003-10-31 15:53 ` Ingo Oeser
2003-10-31 23:02 ` Junio C Hamano
2003-11-01  7:44 ` Sam Ravnborg

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=20031031161450.G4556@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=ian.soboroff@nist.gov \
    --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