Hello, my group was asked to get yaffs2 running under the celinux 2.4.20 
kernel on an arm processor, using one of the Samsung 2k page nand chips.

I've managed to get the March version of MTD running and JFFS2 (though 
it gains CRC errors every time I reset the board.) And I have gotten 
YAFFS2 to compile and partially run, but it is having issues and the 
source files are rather large and uncommented to fix--plus I'm not 
certain whether this would be an MTD or YAFFS2 issue.

At the moment, if I erase the partition and mount, then it looks and 
seems fine. I can copy over files and unmount and remount. However, when 
I reset the board, all erase blocks that were written to get listed as 
bad blocks--so MTD won't allow the YAFFS2 driver to read them again. I 
read that there are some issues with sharing the OOB between MTD and 
YAFFS2, but I wouldn't think either of these would touch the bad block 
markers.

The current configs that I have on for the build (which has gotten me 
the best results) is:
CONFIG_YAFFS_FS
CONFIG_YAFFS_YAFFS2
CONFIG_YAFFS_MTD_ENABLED
CONFIG_YAFFS2_MTD_ENABLED
CONFIG_YAFFS_USE_NANDECC
CONFIG_YAFFS_ECC_WRONG_ORDER (? Seems to work the same with ot without)
CONFIG_YAFFS_USE_GENERIC_RW
CONFIG_YAFFS_USE_HEADER_FILE_SIZE (?)
CONFIG_YAFFS_DISABLE_CHUNK_ERASED_CHECK (?)
CONFIG_YAFFS_USE_OLD_MTD (Didn't start working until I turned this on)

I was also wondering if there was a 2k page version of mkyaffsimage and 
mkyaffs? I didn't want to fiddle with them too much as I'm not sure how 
OOB space is supposed to be split up between MTD and YAFFS2.

Thank you very much,
Chris Williams