I have been trying to integrate a YAFFS2 rootfs on my TI MVL ARM target while enabling the in-band
tagging option of YAFFS.  I've chosen to enable this option is so that it will be compatible
with the HW ECC I've enabled in my kernel and uboot components.  I have followed
various thread on YAFFS2 that suggest I must use SW ECC with YAFFS.  However, the
nature of my target system and its need to upgrade its sub-components (i.e. UBL, UBOOT,
KERNEL, and ROOTFS) in user space require I keep with the HW ECC.  I have followed one thread
(http://www.aleph1.co.uk/lurker/message/20110202.163806.dac21ec5.en.html) which claims
to have achieved HW ECC with YAFFS2, but after attempting to incorporate such, have not had
any success.  Perhaps I just haven't applied its suggested patches properly or mounted the
YAFFS2 fs correctly.  Anyone else had success doing this configuration?

In my efforts, I have also been tackling ECC layout questions w.r.t. UBOOT versus user space
upgrading of components.  My user space component upgrade application now depends
on the default OOB layout enforced by the kernel MTD driver.  I would like to keep this intact
if possible.  I am concerned but also assume that YAFFS2 will not care about which of the
different ECC OOB layouts are in place if it is mounted with the in-band tagging option enabled.
I am hoping that someone may have some further insight on how to coordinate the format
of these components.

Best regards,
Wil


________________________________
NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.