mtd-utils.git, branch v1.1.0

Increment mkfs.jffs2 version number

2007-08-03T13:55:51+00:00

Several change have gone into mkfs.jffs2 since we switch from CVS, but the version number never got incremented. Bump the version number up so people can distinguish between older and newer versions. Signed-off-by: Josh Boyer

Remove $Id:$ tags

2007-08-03T13:49:10+00:00

The $Id:$ tags are left over from the old CVS repository. Several files have since been changed, and they generally have little value in a git repo so they should be removed. Signed-off-by: Josh Boyer

Disable LZO compression by default

2007-08-03T13:34:38+00:00

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

Use lzo2 libraries

2007-07-23T14:15:29+00:00

Switch to using the more common lzo2 libraries for LZO compression. They should still work with the lzo1x interfaces. Signed-off-by: Josh Boyer

Add favourlzo compression mode

2007-07-23T13:11:52+00:00

Add a favourlzo compression mode to mtd-utils This allows lzo compression to be used in the cases where the compression ratio isn't quite as good zlib. This can make sense in certain use cases because LZO decompression is much faster than zlib. Signed-off-by: Richard Purdie Signed-off-by: Josh Boyer

Add lzo support to mtd-utils

2007-07-23T13:11:21+00:00

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 Signed-off-by: Josh Boyer

Add more information to integrity test error message

2007-07-18T12:26:07+00:00

When the integrity test encounters a file that does not contain the expected data, it lists the data that it expected to find in terms of writes to the file. Now the test also displays a list of "raw" writes that includes writes that have been truncated away, or completely overwritten by other writes. The test also now displays the pid because it is used as the initial random seed. Signed-off-by: Adrian Hunter

Correct integrity test calculations of free space

2007-07-18T12:25:59+00:00

Signed-off-by: Adrian Hunter

Amend tests not to insist that file system type is JFFS2

2007-07-18T12:25:44+00:00

Signed-off-by: Adrian Hunter

UBI-utils: add compare feature

2007-07-10T18:00:43+00:00

This is a new feature for pfiflash, called "--compare". It allows the user to simulate a pfiflash session without actually changing the flash content. If the flash content is equal to the data in the pfif file, pfiflash returns zero. A positive value is returned when the flash content differs from the pfi file, which indicates that an update is necessary. This feature is useful when a controller mounts an NFS share during boot and has to determine if a pfi file stored on this share contains a code update. Modified PDD values are also registered by the compare feature. Signed-off-by: Alexander Schmidt