[PATCH] remove support for virtual blocks

[zhao forrest]

>
>	The solution
>
>Quite a few things are possible now.  But any real fix for this design
>problem will require a fixed amount of physical blocks to be part of a
>virtual block.  No matter what else changes, the number of physical
>blocks per virtual one *must not*.
>
>Imo, the best number of physical blocks per virtual one to pick is one
>(1).  Any higher number will limit scalability towards small flashes.
>JFFS2 requires 5 erase blocks in _addition_ to whatever is occupied by
>data.  With a 2:1 mapping, devices smaller than 12 physical blocks
>wouldn't work with JFFS2 at all.
>
>The rest is code and implementation details.
>
Hmm...I think I don't have a very clear picture of implementation
details. In particular I don't have a clear mind of following points:

1 compatibility issue. Let's name the JFFS2 with 1:1 mapping support
as "new", and the JFFS2 without 1:1 mapping as "old". So what's the
expected behaviour of mounting "new" JFFS2 binary upon "old" JFFS2 fs
image? What's the expected behaviour of mounting "old" JFFS2 binary 
upon "new" JFFS2 fs image?

2 Will a new node type be introduced in order to implement 1:1 mapping?

Thanks,
Forrest