[PATCH]Add JFFS2 eraseblock header support

Artem B. Bityutskiy dedekind at infradead.org
Tue Sep 20 07:56:04 EDT 2005

On Tue, 2005-09-20 at 13:36 +0200, Jörn Engel wrote:
> > 
> > If old binary mounts new image, it starts writing its cleanmarkers, use
> > 1:N mapping etc. A "mixed" image appears. Afterwords, if this mixed
> > image is being mounted on new JFFS2 binary, what poor Zhao is supposed
> > to do? There will be too much ugliness in the code to handle that.
> Please don't mix those two problems.  1:1 mapping has been dealt with.
> If you don't like how it has been dealt with, complain in the context
> of 1:1 mapping.

Please, remember the original goal. It is new wear-levelling. This patch
may be considered as something independent, but it is not optimal. If we
follow this way, Zhao must:

1. Write code which understands both cleanmarkers and EB headers.
2. Test that old images are actually work well on new JFFS2.
3. Implement 1:1. Remove cleanmarkers support as they are not needed

So, there is unneeded work. Does it make sense to regard these problems

Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

More information about the linux-mtd mailing list