From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Announce: Software Suspend Core Patch 2.0 rc4.
Date: Sat, 17 Jan 2004 15:07:35 +1300 [thread overview]
Message-ID: <1074305254.2016.13.camel@laptop-linux> (raw)
In-Reply-To: <pan.2004.01.16.21.35.02.327622@dungeon.inka.de>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Hi.
On Sat, 2004-01-17 at 10:35, Andreas Jellinghaus wrote:
> including urls might be nice.
>
> also the feature comparison webpage
> does not mention bios at all.
True. Feel free to produce a column; I don't have any experience with
BIOS support for suspending, so don't know what it can/can't do and
whether this varies from computer to computer.
> Till now I used SOFTWARE_SUSPEND because
> it works fine, whereas PM_DISK somehow uses the
> bios, and does not work (dell latitude c600,
> I don't have that magic partition the dell bios
> expects).
>
> SWSUSP2 will be like SWSUSP concerning this issue?
I'm not sure that PM_DISK does use the bios. In fact, I'm pretty sure it
doesn't. Feel free to prove me wrong.
Regarding the relationship with SOFTWARE_SUSPEND, the answer is yes.
Software Suspend 2 works in a very similar way to Software Suspend.
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-17 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:41 [PREVIEW] Announce: Software Suspend Core Patch 2.0 rc4 Nigel Cunningham
2004-01-16 19:48 ` [Swsusp-devel] " Nigel Cunningham
2004-01-16 21:09 ` Sebastian Kugler
2004-01-16 21:35 ` Andreas Jellinghaus
2004-01-17 2:07 ` Nigel Cunningham [this message]
2004-01-18 18:29 ` Pavel Machek
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=1074305254.2016.13.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=aj@dungeon.inka.de \
--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