public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Ian Soboroff <ian.soboroff@nist.gov>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Post-halloween doc updates.
Date: Sat, 01 Nov 2003 01:56:16 +0800	[thread overview]
Message-ID: <3FA2A240.2060105@metaparadigm.com> (raw)
In-Reply-To: <9cfn0bhjswn.fsf@rogue.ncsl.nist.gov>

On 11/01/03 00:03, Ian Soboroff wrote:
> Russell King <rmk+lkml@arm.linux.org.uk> writes:
> 
> 
>>On Fri, Oct 31, 2003 at 10:06:31AM -0500, Ian Soboroff wrote:
>>
>>>And APM suspend seems to have broken in -test8.  Does it work for
>>>anyone?
>>
>>Doesn't work for me.

APM working here nicely with -test9 on Thinkpad A31. Stilling getting
1394 badness when suspending/resuming with my cardbus 1394 controller
plugged in. Other than that, works pretty seamlessy with no cardbus
cards plugged.

Even radeon with VESA suspend/resume, DRI and X 4.3 (using some
precarious vtswitch calls in /etc/apm/event.d/). wlan-ng works okay
although it requires rmmod/modprobe to wake up properly after resume.

>>Now, taking off my "open source co-operative hat" and placing my
>>"reality" hat on, I'd suggest that anyone who finds that APM doesn't
>>work to consider it a dead loss - It's an obsolete technology, and
>>therefore no one is interested in it anymore.  I've reported the
>>problem multiple times here and there's been very little, if any,
>>reaction, so this seems to back that up.

Hmmm, well for me; a working APM (here) is much prefered to non-
working ACPI suspend/resume. I'd prefer not to obsolete APM until
there is a working alternative (with mature userspace tools).

~mc


  parent reply	other threads:[~2003-10-31 17:56 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
2003-10-31 17:56       ` Michael Clark [this message]
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=3FA2A240.2060105@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --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