From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
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 13:55:19 +0200 [thread overview]
Message-ID: <20060330115519.GN8485@elf.ucw.cz> (raw)
In-Reply-To: <200603301944.27188.ncunningham@cyclades.com>
Hi!
> > > > 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).
>
> I just found the line saying pciutils-devel is needed. Maybe that will make
> the difference.
I do not see missing includes, so I'm not sure it will help. Can you
try adding
ARCH=x86_64
to Makefile?
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-30 11:55 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
2006-03-30 11:55 ` Pavel Machek [this message]
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=20060330115519.GN8485@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=ncunningham@cyclades.com \
/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.