Hi.
When I do for example the following thing:
root@htcdream ~ # ubiformat /dev/mtd3 -f shr-fso2-demo-image-eglibc-ipk--20100613-htcdream.rootfs.ubifs -s 2048
ubiformat: mtd3 (nand), size 70778880 bytes (67.5 MiB), 540 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 0 -- 0 % complete libmtd: error!: cannot read 64 bytes from mtd3 (eraseblock 0, offset 0)
error 22 (Invalid argument)
ubiformat: error!: failed to scan mtd3 (/dev/mtd3)
Or just:
root@htcdream ~ # ubiformat /dev/mtd3 -s 2KiB
ubiformat: mtd3 (nand), size 70778880 bytes (67.5 MiB), 540 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 0 -- 0 % complete libmtd: error!: cannot read 64 bytes from mtd3 (eraseblock 0, offset 0)
error 22 (Invalid argument)
ubiformat: error!: failed to scan mtd3 (/dev/mtd3)
I can extract the following error by dmesg:
[12521.267852] msm_nand_read_oob: unsupported ops->len, 64
I saw the following post:
http://patchwork.ozlabs.org/patch/50601/
This was the solution for our kind of problem.
But our driver seems to be deplaced and in consquence of this, it does not draw benefit of the full NAND framework power.
Please correct me if I'm wrong. But I do not have ANY clou, how I could propagate the disablement of subpage size
capability for this driver.
Best regards
leviathan
Attachment:
signature.asc
Description: This is a digitally signed message part.
