MTD utils v1.5.0: MEMERASE64 ioctl failed error

[Mike Frysinger]

On Tuesday 15 October 2013 04:32:23 Shah, Minal wrote:
> Hi Brian,
> Thanks a lot for the explanation; I understood the reason for failure.
> 
> > So why do you want to erase bad blocks?
> 
> The reason why I want to erase bad blocks is because they actually don't
> seem to be bad. Block0 itself is shown as bad.
> I have few partitions (like MLO and u-boot env) of size equal to 1 erase
> block. The block is marked as bad and hence I cannot write anything to
> this partition. One of the solutions is to increase that partition size to
> 2 blocks so even if 1 block is bad then it will atleast be able to write
> to the other block of the same partition. But I don't think I should do
> this while the block is not really bad (what if all the blocks for some
> reason are marked as bad while they are actually not).
> 
> This question came in my mind from the fact that "nand scrub" command is
> allowed from u-boot which allows to also completely erase all the bad
> blocks; so why not from the kernel level.

as mentioned, there was discussion some time ago about adding this 
functionality.  but the work never finished.  if you're interested, i'd suggest 
picking up the work there.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20131015/6332a49b/attachment.sig>