mtd nand erase and bad block

[Artem Bityutskiy]

On Mon, 2012-07-02 at 08:14 +0100, Angus CLARK wrote:
> On 06/29/2012 11:31 AM, Artem Bityutskiy wrote:
> > On Wed, 2012-06-27 at 13:37 +0100, Angus CLARK wrote:
> >> However, for case 2, I just want to force the erase operation so I can wipe the
> >> BBTs and return the device as close as possible to its original state.  We could
> >> put some logic in the kernel, "if 'MEMBBSCRUB" on BBT blocks, do not
> >> update/rewrite BBTs", but I think this "policy" decision would be better handled
> >> in userspace.
> > 
> > Sounds like you need 2 separate ioctls:
> > 1. MEMBBSCRUB
> 
> There are occasions when it is useful to unmark a bad block, but without erasing
> first.  Therefore, I guess my preference would be to split this further:
> 'erase-bad-block' and 'mark-block-as-good'.

I can smell over-engineering - any good example? Note, you will leave
unused bytes in the ioctl data structure an make it extandable in the
future.

-- 
Best Regards,
Artem Bityutskiy
-------------- 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/20120703/bd065b65/attachment.sig>