Lines Matching refs:blocks
13 Print a list of all of the bad blocks in the current device.
26 and write commands). Only complete erase blocks can be erased.
35 This command will not erase blocks that are marked bad. There is
36 a debug option in cmd_nand.c to allow bad blocks to be erased.
37 Please read the warning there before using it, as blocks marked
52 for bad blocks or ECC errors.
59 As JFFS2 skips blocks similarly, this allows writing a JFFS2 image,
61 bad blocks. Compact images, such as those produced by mkfs.jffs2
63 going to be trouble if there are any bad blocks.
79 for bad blocks.
292 using both the new code which is able to skip bad blocks
301 DANGEROUS!!! Factory set bad blocks will be lost. Use only
302 to remove artificial bad blocks created with the "markbad" command.
313 automate retries and handling of possibly newly detected bad blocks if the
321 Optionally, a second parameter size can be given to test multiple blocks with
324 command returns 0 if all tested blocks have been found reliable, else 1.