public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Mark Lord <lkml@rtr.ca>, linux-kernel@vger.kernel.org
Subject: Re: Suspend2-2.2.2 for 2.6.16.
Date: Thu, 30 Mar 2006 19:44:23 +1000	[thread overview]
Message-ID: <200603301944.27188.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060330092627.GG8485@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Thursday 30 March 2006 19:26, Pavel Machek wrote:
> On St 29-03-06 20:50:27, Nigel Cunningham wrote:
> > Hi.
> >
> > On Wednesday 29 March 2006 19:19, Pavel Machek wrote:
> > > On Út 28-03-06 18:51:51, Mark Lord wrote:
> > > > Nigel Cunningham wrote:
> > > > >Hi everyone.
> > > > >
> > > > >Suspend2, version 2.2.2 is now available from
> > > > >
> > > > >http://stage.suspend2.net/downloads/all/suspend2-2.2.2-for-2.6.16.ta
> > > > >r.bz 2
> > > >
> > > > Wow!  Is this ever freaking fast!
> > > > Try it folks.  Once you do, you'll never go back to the slow way!
> > >
> > > Please do try code at suspend.sf.net. It should be as fast and not
> > > needing big kernel patch.
> >
> > Don't bother suggesting that to x86_64 owners: compilation is currently
> > broken in vbetool/lrmi.c (at least).
>
> It seems to work at least for some users. I do not have x86-64 machine
> easily available, so someone else will have to fix that one.
>
> (Also it should be possible to compile suspend without s2ram support,
> avoiding the problem).
> 								Pavel

I just found the line saying pciutils-devel is needed. Maybe that will make 
the difference.

Regards,

Nigel

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-03-30 11:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  6:01 Suspend2-2.2.2 for 2.6.16 Nigel Cunningham
2006-03-28 10:50 ` Pavel Machek
2006-03-28 23:51 ` Mark Lord
2006-03-29  9:19   ` Pavel Machek
2006-03-29 10:50     ` Nigel Cunningham
2006-03-30  9:26       ` Pavel Machek
2006-03-30  9:35         ` Arkadiusz Miskiewicz
2006-03-30  9:44         ` Nigel Cunningham [this message]
2006-03-30 11:55           ` Pavel Machek
2006-03-30 11:59             ` Nigel Cunningham
2006-03-30 12:05               ` Pavel Machek
2006-03-30 12:17                 ` Rafael J. Wysocki
2006-03-30 12:24                   ` Rafael J. Wysocki
2006-03-30 12:59                     ` Pavel Machek
2006-03-30 16:20                       ` Rafael J. Wysocki
2006-03-30  9:34       ` Rafael J. Wysocki
2006-03-30  9:39         ` Nigel Cunningham
2006-03-30 11:57           ` Matthew Garrett
2006-03-30 12:13           ` Rafael J. Wysocki
2006-03-30 23:14             ` Nigel Cunningham
2006-03-31  8:12               ` Rafael J. Wysocki

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=200603301944.27188.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=pavel@ucw.cz \
    /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