From: Pavel Machek <pavel@ucw.cz>
To: Jan Rychter <jan@rychter.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How does one get paid to work on the kernel?
Date: Tue, 23 Sep 2003 14:07:16 +0200 [thread overview]
Message-ID: <20030923120715.GA11901@openzaurus.ucw.cz> (raw)
In-Reply-To: <m2he38r7ji.fsf@tnuctip.rychter.com>
Hi!
> Nigel> There is support in the current kernel for Software Suspend, but
> Nigel> the 2.4 version contains a lot of extra functionality that isn't
> Nigel> present in 2.6 at the moment. (Support for HighMem, swap files,
> Nigel> asynchronous I/O, a nicer user interface, compression...).
>
> Nigel is being modest and doesn't mention that the 2.4 version actually
> works, which is possibly its biggest advantage.
2.6.0-test3 swsusp should work, too, unless you have driver problem.
With ext2, ide and vesafb you should be able to suspend/resume
correctly.
That might not be practical for you, but should be
good enough for fixing drivers.
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
prev parent reply other threads:[~2003-09-25 7:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 20:02 How does one get paid to work on the kernel? Nigel Cunningham
2003-09-19 7:51 ` Måns Rullgård
2003-09-19 7:59 ` Nigel Cunningham
2003-09-19 8:10 ` Måns Rullgård
2003-09-19 9:31 ` Nigel Cunningham
2003-09-19 9:45 ` Resuming from software suspend [was: Re: How does one get paid to work on the kernel?] Måns Rullgård
2003-09-19 10:05 ` Nigel Cunningham
2003-09-19 10:15 ` Resuming from software suspend Måns Rullgård
2003-09-19 10:27 ` Nigel Cunningham
2003-09-19 11:09 ` Måns Rullgård
2003-09-19 10:40 ` Pavel Machek
2003-09-19 13:34 ` Bas Mevissen
2003-09-19 13:40 ` How does one get paid to work on the kernel? Bas Mevissen
2003-09-19 13:51 ` Måns Rullgård
2003-09-19 13:58 ` Bas Mevissen
2003-09-19 14:09 ` Måns Rullgård
2003-09-19 17:51 ` Jan Rychter
2003-09-23 12:07 ` Pavel Machek [this message]
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=20030923120715.GA11901@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox