Re: nanddump badblock options

Mike Frysinger
2011-06-20T19:23:10Z

On Wed, Jun 8, 2011 at 16:01, Brian Norris wrote:
> I have some ideas to implement in nanddump regarding the variety of bad block
> handling options. I thought I'd at least get some feedback before working up a
> full patch, so please comment on my ideas.

your ideas sound good to me

> (4) Can Mike provide a good explanation for --bb=omitbad in the table below? I
> personally don't understand it's exact use, nor do I know how to describe it
> best (to provide contrast against the other options), but I understand that you
> would like to keep the option. I would appreciate some help.
>
> (5) Summary table:
>
> -----------------------------------------------------------------------------------------------------------------
>  Old option         New option                   Comment
> -----------------------------------------------------------------------------------------------------------------
>  <default>     =>   --bb=padbad                  dump flash data, substituting 0xFF for any bad blocks

maybe add a pad option so people can specify the data rather than just
0xff ? although that's probably just overkill and no one would
actually use it ...

>  --noskipbad   =>   --bb=dumpbad                 dump flash data, including any bad blocks
>  --skipbad     =>   --bb=skipbad, <default>      dump good data, completely skipping any bad blocks (new default)
>  --omitbad     =>   --bb=omitbad                 (dump flash data, substituting nothing for any bad blocks?)

i think omitbad is covered by the other options. the one i'm really
concerned in keeping is --bb=dumpbad for cases where the bbt says it's
bad, but it isnt really, so i want the data unmolested.
-mike