Charles Manning <manningc2 <at> actrix.gen.nz> writes:


> This whole area is unfortunately rather messy. The oob handling in mtd is 
> often broken and messy and there are many details to get right. Since jffs2 
> does not use oob, changes don't get fixed there unless yaffs-inclided people 
> do things.
> 
> This leads to people trying to work around problems on the yaffs side which 
> might not be the "correct and pure" place to fix these issues, but is often 
> the simplest. As a result there is no standard mechanism that works for all.
> 
> I do have some inband-tags code which is still experimental (though looks 
> pretty robust). This does not use oob for the tags. This makes for simpler 
> integration (no oob headaches) - which is a bit of a cop-out. Power-of-2 
> alignment is lost which causes some performance loss, but likely not much. 
> inband-tags uses yaffs2 mode even on 512-byte page devices which makes 
> checkpointing available on 512-byte page devices.

shouldn't these issues be brought to mtd's developers attention and establish a
channel of communication in order not to break yaffs backward compatibility with
devices such as the routerboard 1xx & 5xx?

can we at least open a ticket about it?