[PATCH 6/7] New utility ubidump

[hujianyang]

> 
> Things like UBI volume table, UBI fast-map stuff are not "headers", so I
> am not sure if using word "headers" a good idea. Probably we want
> options like --ubifs and --ubi to denote ubi and ubifs-level stuff. The
> default would be "everything".
> 
> But again, if you start smaller, and upstream a good tool for
> UBIFS-level stuff, it will be easier to add UBI stuff separately.
> 
> Besides, I have some additional vision, which you do not have to
> implement, but which should be taken into account. E.g., ubidump which
> does not need UBI/UBIFS drivers, ubidump which can deal with an image
> generated with nanddump without "mounting" it, etc. So I was thinking
> doing small steps at a time would make it easier for me and for you to
> make a tool which has limited functionality today, but which can be
> later extended to support more functionality.
> 

It seems you what more than me. I think you are right. I need to
reconsider how to realize these above, not hole of them, but a
good architecture that can be extended easily.

So I think getting data from mtd driver is a good choice and then
run it with an image file. Current UBI functionality has lots of
limit and it is basing on UBI driver. But we need to do more work
in user space (rebuilding volume table and so on) in this way. I
think it's worth.

Give me some time to re-create this utility. I will send it to you
if I finished it. If you get some new ideas, please tell me as soon
as possible.

Thanks~!

Hu