mtd nand erase and bad block

[Angus CLARK]

Hi Brian,

On 06/14/2012 06:48 PM, Brian Norris wrote:
> On Tue, Jun 5, 2012 at 5:17 AM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
>> On Fri, 2012-06-01 at 17:54 +0300, Shmulik Ladkani wrote:
>>>
>>> My personal preference would be:
>>> 1. A new ioctl (MEMSCRUB?)
>>> 2. debugfs flag, PER MTD PART (slightly safer than your global flag)
>>> 3. global debugfs flag
[snip]
> I like the idea of an ioctl (option 1), since that does not require
> recompilation (even in the event that debugfs wasn't enabled) and can
> be built into a user-space tool, with appropriate warnings and
> prompting for the user, of course. The debugfs ideas seem a little bit
> too manual to be useful for anyone but a true driver/kernel developer
> and also a little bit too unsafe (a user may want to target a specific
> block without disabling bad block checking for all chips or even for
> the entire partition).
> 

Yes, I agree, option 1 is looking good.  The main motivation behind option 3 was
to add support with minimal code changes, but option 1 is a cleaner solution.

> 
> So Angus, are you going to code this?
> 

Yes, I will have go later today or early next week...

Cheers,

Angus