State of UBI

[dedekind]

Hello Josh,

>Where are we with UBI?  It seems Artem has been steadily committing
>fixes to the ubi git tree. 
Yes, I'm using it in another project so I stedily add more tiny
features, changes and fixes. Also, one may notice that I maintain
UBI FAQ which has considerably grown.

>I think a good start would be to list what's missing.  I know that it
>needs a patch to allow double page writes on NAND.  There's also the
>missing JFFS2 integration, or rather two competing versions of it.  Is
>there anything else?  Something documented in a TODO list would be
>good.

Well, what you've listed is not what UBI itself needs:
1. "double page writes on NAND" - it needs MTD changes and zero UBI changes.
2. JFFS2 integration also requires zero changes in UBI (as long as it is
sane).

But, well, this is not to start a new contest :-) Let's list want to
have in UBI and around UBI.

I'd add here then:

1. True and extensive unclean reboot testing.
2. Better UBI utilities as I find the current ones not ideal.

>Then there's a matter of when should it be merged.  As it stands right
>now, UBI is in limbo and I'd hate to see something with good potential
>just sit around rotting.  Having a merge goal would perhaps provide
>some motivation.  It could be a date or a kernel version, but it
>should be realistic.

Would be nice to just add it to mtd-2.6.git, IMO. This would be a good
and simple step further.

>So lets come up with some kind of plan to get it reviewed, tested, and
>merged.  My hope would be that all involved so far, or even those that
>want to help out, could reply with their thoughts.  I'm afraid some
>won't for various reasons.  Perhaps if some of us are going to LCA we
>could get together and hash some things out more in detail, but I'd
>rather not wait until then to get things moving.

I think that we should just to merge it with mtd-2.6.git. And all the
promotion stuff may go in parallel. I'm not sure about the plan... LCA
sounds great.

I can only say that I'm going to use it extensively. And I'm already
thinking about a new - scalable UBI implementation.

Artem.