From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swsusp bootsplash support
Date: Mon, 12 Jul 2004 06:43:14 -0700 [thread overview]
Message-ID: <m21xjh1gul.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: 20040709155614.GA8426@linux.nu
>>>>> "Erik" == Erik Rigtorp <erik@rigtorp.com> writes:
Erik> On Fri, Jul 09, 2004 at 12:55:31PM +0100, Dave Jones wrote:
>> Personally I'd prefer the effort went into making suspend actually
>> work on more machines rather than painting eyecandy for the minority
>> of machines it currently works on.
Erik> Miniority? Well both swsusp and pmdisk has worked on the majority
Erik> of machines I've come across. From what I understand swsusp works
Erik> on almost all x86 uniprocessor machines and that's a lot of
Erik> machines. Some drivers are a hassle though.
FWIW, I have been using Nigel's swsusp2 for a long time now on a 2.4
kernel. It has been exceptionally well-behaved and stable. And it's an
extremely important part of my Linux world. I will not move to 2.6
unless I'm sure swsusp2 will work well.
In fact, it seems to me that many kernel developers underestimate the
importance of software suspend to actual real Linux users. I guess when
you reboot your monster PC rig five times a day to upgrade kernels, you
don't much care. But if you use a laptop and you actually care about
opening it and getting a stable, working environment within 20s, trust
me -- software suspend becomes more important to you than all the
scheduler improvements in the world.
I would gladly trade all the performance improvements of the last couple
of years for a stable, working swsusp2 and a USB subsystem which doesn't
a) prohibit my CPU from using C3 sleep and b) crash and burn regularly
bringing the whole machine down with it.
--J.
next prev parent reply other threads:[~2004-07-12 1:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 11:05 [PATCH] swsusp bootsplash support Erik Rigtorp
2004-07-08 13:39 ` Christoph Hellwig
2004-07-08 20:48 ` Pavel Machek
2004-07-08 21:04 ` Christoph Hellwig
2004-07-08 22:52 ` Pavel Machek
2004-07-08 22:55 ` Christoph Hellwig
2004-07-08 23:23 ` Dave Jones
2004-07-09 5:15 ` Pavel Machek
2004-07-09 11:55 ` Dave Jones
2004-07-09 12:19 ` Nigel Cunningham
2004-07-09 14:27 ` Bartlomiej Zolnierkiewicz
2004-07-09 22:00 ` Nigel Cunningham
2004-07-09 15:56 ` Erik Rigtorp
2004-07-12 13:43 ` Jan Rychter [this message]
2004-07-12 3:21 ` Eric Altendorf
2004-07-10 12:34 ` Pavel Machek
2004-07-14 11:27 ` Jan Rychter
2004-07-09 8:36 ` Erik Rigtorp
2004-07-09 14:48 ` Stefan Reinauer
2004-07-09 15:01 ` Dave Jones
2004-07-09 20:44 ` Diego Calleja García
2004-07-09 21:49 ` Erik Rigtorp
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=m21xjh1gul.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
--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 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.