| Age | Commit message (Collapse) | Author |
|---|
|
the compress size parameter in lzo is defined in the header file as lzo_uint.
This looks very much like uint32_t, I know, but is defined as unsigned long.
So on 64bit LE systems we zero some bytes near by and on BE systems we
get a size of zero.
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
This is the same bug as in kernel, pointed out the LZO author
(Markus Oberhumer):
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f2a11b158a24301e9158e9c873fa88e5eb775486
Signed-off-by: Riku Voipio <riku.voipio@iki.fi>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
When the recent LZO compression support went into mtd-utils recently,
it was enabled by default. This means that mkfs.jffs2 will default to
creating images with lzo compression as the default.
Older kernels cannot decompress such images, so lzo should be disabled
by default. The patch below fixes this. To enable lzo compression
from now on, simply pass '-X lzo' as an option to mkfs.jffs2.
Signed-off-by: Josh Boyer <jwboyer@gmail.com>
|
|
Switch to using the more common lzo2 libraries for LZO compression. They
should still work with the lzo1x interfaces.
Signed-off-by: Josh Boyer <jwboyer@gmail.com>
|
|
Add LZO support to mtd-utils to generate LZO compressed jffs2 images
Unlike the kernel version, the standard lzo userspace library is used
along with lzo1x_999_compress rather than the lzo1x_1_compress version
since better compression ratios can be obtained (at no significant cost
to decompression time).
Signed-off-by: Richard Purdie <rpurdie@openedhand.com>
Signed-off-by: Josh Boyer <jwboyer@gmail.com>
|
