From: Marc Lehmann <pcg@schmorp.de>
To: Michael Frank <mhf@linuxmail.org>
Cc: Pavel Machek <pavel@suse.cz>,
Software Suspend - Mailing Lists
<swsusp-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] (no subject)
Date: Thu, 25 Mar 2004 16:18:02 +0100 [thread overview]
Message-ID: <20040325151802.GD11633@schmorp.de> (raw)
In-Reply-To: <opr49atvpk4evsfm@smtp.pacific.net.th>
On Mon, Mar 22, 2004 at 05:18:57PM +0800, Michael Frank <mhf@linuxmail.org> wrote:
> Also, as Pavel mentioned, LZF code should be put in /lib and cleaned up.
I fully agree. Unfortunately, I have about zero time for any such project
in the foreseeable future (It'd need more time since my knowledge about
integration issues is extremely scarce, and I am swamped with other work).
The code in the kernel required a few features not available with earlier
lzf releases (e.g. passing the the hash table via args instead of
allocating it on the stack).
The standard 1.3 release is configurable via defines in this respect
(-DAVOID_ERRNO -DLZF_STATE_ARG), and would be better suited for inclusion
in the kernel (the code would be byte-identical in the userspace and
kernel version), but making a patch would require some testing, to make
sure the new code compiles etc.
Also, as used in software-suspend2, the user must #define symbols (see
the beginning of kernel/power/lzfcompress.c) and include the c files
directly. When making them library functions one would need to choose
a reasonable default. Copying lzfP.h into include/linux and editing it
should be enough, though.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
prev parent reply other threads:[~2004-03-25 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 9:18 Michael Frank
2004-03-22 9:40 ` [Swsusp-devel] (no subject) Cameron Patrick
2004-03-22 9:49 ` Arjan van de Ven
2004-03-22 10:02 ` LZF inclusion in kernel Michael Frank
2004-03-22 18:21 ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-23 11:47 ` Arjan van de Ven
2004-03-25 15:02 ` Marc Lehmann
2004-03-24 22:20 ` Nigel Cunningham
2004-03-25 14:26 ` Marc Lehmann
2004-03-25 14:56 ` Pavel Machek
2004-03-28 0:43 ` Marc Lehmann
2004-03-22 10:15 ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 15:18 ` Marc Lehmann [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=20040325151802.GD11633@schmorp.de \
--to=pcg@schmorp.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=pavel@suse.cz \
--cc=swsusp-devel@lists.sourceforge.net \
/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