mtd-utils.git/ubi-utils, branch v1.5.0

mtdinfo: correct grammar on error message

2012-02-14T09:00:13+00:00

Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

mtdinfo: fix `--all' for non-consecutive device numbers

2012-02-02T11:25:14+00:00

When we have assigned non-consecutive device numbers to our MTD devices, then we run `mtdinfo --all', we get errors once mtdinfo tries to process the devices in the "hole". For instance, suppose that at boot time, we have one MTD (/dev/mtd0) then perform a sequence like the following: # modprobe mtdram # modprobe nandsim # rmmod mtdram Then at this point, we have should have devices 0 and 2 without 1. Then: # mtdinfo --all ... mtdinfo: error!: mtd1 does not correspond to any existing MTD device We add a check to first see if device is present, then continue to the next ID if it doesn't exist. Reported-by: Brian Foster Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

ubinfo: fix `--all' for non-consecutive device numbers

2012-01-27T14:55:24+00:00

When we have assigned non-consecutive device numbers to our UBI devices, then we run `ubinfo --all', we get errors once ubinfo tries to process the devices in the "hole". For instance, suppose there are two UBI devices, /dev/ubi0 and /dev/ubi10; then, ubinfo will fail trying to open /dev/ubi1 with: ubinfo: error!: cannot get information about UBI device 1 error 2 (No such file or directory) This patch adds a check to first see if device is present, then continue to the next ID if it doesn't exist. Reported-by: Brian Foster Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

libubi: make `ubi_dev_present()' a library function

2012-01-27T14:55:24+00:00

We will use this function in ubinfo. Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

Merge branch 'brian'

2011-11-18T21:53:11+00:00

mtdinfo: provide info when used without arguments

2011-11-17T22:22:11+00:00

If the user specifies neither a MTD argument nor the `-a' flag, we print a cryptic message; i.e., # mtdinfo libmtd: error!: cannot get information about "(null)" error 14 (Bad address) mtdinfo: error!: cannot get information about MTD device "(null)" error 14 (Bad address) This is a regression; previously, mtdinfo would give some short info about number of devices, etc. when used without arguments. To fix this, we revert commit d53c03b0989f8354a7e4dbb947a150fc7fe3f6d1 and call print_general_info() when no device is specified. Signed-off-by: Brian Norris Acked-by: Mike Frysinger Signed-off-by: Artem Bityutskiy

ubiformat: handle write errors correctly

2011-09-19T04:52:49+00:00

This issue was reported and analyzed by Anton Olofsson : when ubiformat encounters a write error while flashing the UBI image (which may come from a file of from stdout), it correctly marks the faulty eraseblock as bad and skips it. However, it also incorrectly drops the data buffer which was supposed to be written, and reads next block of data. This patch fixes this issue - in case of a write error, we preserve the current data and write it to the next eraseblock, instead of dropping it. Signed-off-by: Artem Bityutskiy

libmtd: modify `mtd_write' to cover OOB writes

2011-09-11T13:11:41+00:00

To support the MEMWRITE ioctl, we will need a different sort of libmtd interface for writing to flash. We will expand mtd_write to include more functionality; for now, we just change the function definition and description as we begin to add the actual functionality. Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

mkfs.ubifs/ubinize: increase PEB size limit to 2MiB

2011-08-20T04:07:37+00:00

Signed-off-by: Artem Bityutskiy

mtdinfo: consolidate help as display_help()

2011-08-16T14:14:14+00:00

The help message for mtdinfo is unnecessarily disjointed. It is split into three strings which reuse the PROGRAM_NAME string inefficiently and don't have a consistent style. This fixup should provide a cleaner look with aligned columns and easier-to-read source code. Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy