| Age | Commit message (Collapse) | Author |
|---|
|
... with the stupidest possible algorithm for storing them and looking
them up. Optimising that is simple enough, but left as an exercise for
the user. This is userspace, after all. It's not as if I care.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
...because when we support hard links we'll want to preserve the
original inode numbers...
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: Josh Boyer <jwboyer@gmail.com>
|
|
in 2.6.21.
Signed-off-by: Josh Boyer <jwboyer@gmail.com>
|
|
Fixed a problem when ECC was checked. The correction was not properly
done by subpage. Added more output for the moment to be able to figure
out more potential problems.
Added testcase: bin2nand2bin.sh and biterror inject program inject_biterror.pl
Interface
o ECC correction disabled by default. Switch to turn it
explicitly on. The user must specify what he wants to be done.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
The number is usefull to analyze cards with broken flash content.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
The extraction of data from blocks used for dynamic volumes was
totally broken. The data size was calculated wrong. This fix is not
perfect, the alignment is still ignored.
The parameter "header-size" is very misleading. It does not reflect
the vid hdr offset properly. I assume therefor that it only works for
the layout I am using where the vid hdr is at the _end_ of the 1st
NAND page (2048).
I added the generation of a textfile with information about the blocks
which are going into the internal graph representation.
Instead of a graph I think that a simple array will simplify the code
very much. The array must than be sorted properly to cope with older
and newer block-copies but that should not be a problem.
discussed the tool with my coleage Andreas Arnez and we found that it
might be a good idea to replace it even with a perl program for the
same purpose since that would offer the flexibility to change it on
the fly when needed. The tool is mainly used for crash analysis so it
could be an advantage to change it without needing a C-compiler.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
We have no good testcases for this kind of tool yet. Adding a 1st
draft.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
Drake Dawsett had done some changes to our unubi which where not yet
published. I hereby send his latest code and integrated the parameter
handling which was changed in our version. When reviewing this very
huge patch we need to ensure that possible changes of others are not
reversed.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
This patchset migrates the remaining tools (pddcustomize, ubimirror and
pfiflash) to the new libubi.
Signed-off-by: Alexander Schmidt <alexs@linux.vnet.ibm.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
When bad blocks occur more debug information is needed.
To identify the bad blocks the blocksize is required.
The split block mode was added to generate files per
block. In split mode the bad block markers are analyzed
and a summary is printed at the end.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
The filename for the OOB data was wrongly assigned.
OOB data could therefore not be dumped.
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
|
|
Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Just silly hacks. Also remove udevsettle() invocation from UBI
library. If it must be called, it is not library's business
anyway. Wa added it to make scripts which use ubimkvol utility
run, so it is the only caller that really needs this. So
just move the cruft to the utility.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Rename __unused to ubi_unused to avoid clashes with system namespace
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
This halves the FEC decode time and doesn't seem to hurt the error rate
much.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Send one packet from each eraseblock in turn, rather than all packets
for one eraseblock together. This means that bursts of loss are evenly
spread between blocks. It also makes the client side a bit more complex
if you can't assume that there's anywhere except the flash to store its
intermediate data.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
in round-robin fashion rather than full blocks one at a time.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
|
|
Paper: http://info.iet.unipi.it/~luigi/mccr6.ps.gz
Code: http://info.iet.unipi.it/~luigi/rmdp980703.tgz
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Creates the volume with maximum available size
Signed-off-by: Zoltan Sogor <weth@inf.u-szeged.hu>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
|
|
It just busy-waits until it's time to send the next packet now. Which
sucks, but gives us good timing for debugging. Needs work (and actually
if we have hrtimers we probably _can_ sleep and still have proper
timing).
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|
|
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 <jwboyer@gmail.com>
|
|
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 <jwboyer@gmail.com>
|
|
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 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 <rpurdie@openedhand.com>
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>
|
|
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 <ext-adrian.hunter@nokia.com>
|
|
Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
|
|
Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
|
|
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 <alexs@linux.vnet.ibm.com>
|
