All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: ML ACPI-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: [Ipw2100-devel] [susp-resume] ipw2100 suspend patch for 0.54 (version 3)
Date: Wed, 15 Sep 2004 13:30:38 +0200	[thread overview]
Message-ID: <20040915113038.GB17317@hell.org.pl> (raw)
In-Reply-To: <41481805.8020106-wlebWZzHoyE@public.gmane.org>

Thus wrote Luca Capello:
> I can *successfully* suspend/resume with the 2 calls (/proc or /sys),
> directly from XFree86 and with all the modules loaded. As already
> reported, the only difference is that with the /sys call, in suspending
> I've always the machine which powers off, while with the /proc call I
> should power off the machine by pressing 4-sec the power button.
> 
> Simple question: which should be the best method to use? /sys or /proc?

Use /sys if it works. OTOH, /proc is more tested and actively maintained.
ACPI S4 triggered by /sys is slightly better in handling wake-up events
(think Wake On LAN, RTC) and other things like, say AC status updates.

> Another thing: why for the /sys call I should use 'append=noresume',
> while I want to *resume*? I mean, it's not so clear...

Because /sys is the pmdisk code, /proc is swsusp1 code (at least until the
merge in -mm kernels goes into mainline). swsusp1 uses resume and noresume,
pmdisk uses pmdisk (=/dev/hdXY) and, well... AFAIR pmdisk (="").
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m

  parent reply	other threads:[~2004-09-15 11:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3ACA40606221794F80A5670F0AF15F8403BD570F@pdsmsx403>
2004-09-08 10:41 ` [Ipw2100-devel] [susp-resume] ipw2100 suspend patch for 0.54 (version 3) Luca Capello
     [not found]   ` <413EE1EA.2070307-wlebWZzHoyE@public.gmane.org>
2004-09-08 13:02     ` Luca Capello
     [not found]       ` <413F02E7.3060005-wlebWZzHoyE@public.gmane.org>
2004-09-14 22:29         ` Pavel Machek
     [not found]           ` <20040914222905.GA17380-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-09-15  0:04             ` Luca Capello
     [not found]               ` <4147870C.9090003-wlebWZzHoyE@public.gmane.org>
2004-09-15  8:37                 ` Karol Kozimor
     [not found]                   ` <20040915083734.GA17317-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-09-15 10:23                     ` Luca Capello
     [not found]                       ` <41481805.8020106-wlebWZzHoyE@public.gmane.org>
2004-09-15 11:30                         ` Karol Kozimor [this message]
2004-09-17  8:51                 ` Pavel Machek
     [not found]                   ` <20040917085110.GA22859-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-09-27 11:54                     ` Luca Capello
     [not found]                       ` <4157FF69.7040204-wlebWZzHoyE@public.gmane.org>
2004-09-28 13:29                         ` Luca Capello

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=20040915113038.GB17317@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.