On 12/12/05, Michael Arm <
micharmel@gmail.com> wrote:
> If we add a byte to the head of the yaffs_PacketTags2 struct, and set it to
> 0xFF in yaffs_PackTags2(), then everything works fine and data can be read
> and written good, apparently. However I am wondering if this is a good fix,
> or if there are hidden problems that this might be cause due to the new
> offset of the rest of OOB data and the possibility of a byte of OOB data
> being lost at the end.
I ended up doing this in my YAFFS2 backport to a 2.4 kernel. I'm sure
the correct fix is for the MTD layer to correctly support the OOB data
on 2K pages - I thought it did in mainline?
Jon.
(text/plain)