From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Ducrot Bruno'" <poup@poupinou.org>, Pavel Machek <pavel@suse.cz>
Cc: Ducrot Bruno <ducrot@poupinou.org>,
Patrick Mochel <mochel@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: RE: [ACPI] Re: [2.5.50, ACPI] link error
Date: Mon, 9 Dec 2002 11:12:43 -0800 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A581@orsmsx119.jf.intel.com> (raw)
> From: Ducrot Bruno [mailto:poup@poupinou.org]
> > I think that s4bios is nice to have. Its similar to S3 and easier to
> > set up than swsusp... It would be nice to have it.
>
> for me:
> pros:
> -----
> 1- it is really really more easier to implement than S4;
> 2- we can even have it with 2.4 kernels (it seems that it work without
> the need of freezing processes, but I suspect that this statement
> is 'wrong' by nature).
>
> cons:
> -----
> 1- it is much slower (especially at save time) than your swsusp;
> 2- end users must setup their systems (need to create a
> suspend partition,
> or to keep a vfat partition as the really first one (/dev/hda1));
> 3- we use a bios function. Actually, everything can happen...
>
> That why I prefer swsusp at this time, or any other
> implementation of S4 (I
> think about an implementation of S4 via LKCD).
I concur with your pros and cons. This makes me think that if S4BIOS support
ever gets added, it should get added to 2.4 only.
Regards -- Andy
next reply other threads:[~2002-12-09 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 19:12 Grover, Andrew [this message]
2002-12-10 0:49 ` Alan Cox
2002-12-10 20:40 ` Pavel Machek
2002-12-10 20:50 ` Andrew McGregor
2002-12-11 3:44 ` [ACPI] Dell i8k was: " Andrew McGregor
2002-12-11 10:14 ` [ACPI] " Ducrot Bruno
2002-12-11 16:00 ` Alan Cox
2002-12-11 10:07 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 22:40 Pavel Machek
2002-12-05 22:43 ` Patrick Mochel
2002-12-06 0:06 ` Pavel Machek
2002-12-06 18:57 ` [ACPI] " Ducrot Bruno
2002-12-06 23:05 ` Ducrot Bruno
2002-12-08 19:49 ` Pavel Machek
2002-12-08 20:46 ` Constantinos Antoniou
2002-12-09 10:40 ` Ducrot Bruno
2002-12-09 10:28 ` Ducrot Bruno
2002-12-09 11:01 ` Pavel Machek
2002-12-09 17:42 ` Ducrot Bruno
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=EDC461A30AC4D511ADE10002A5072CAD04C7A581@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ducrot@poupinou.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@suse.cz \
--cc=poup@poupinou.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
all inboxes | Powered by JetHome®