imcd, et al,

  Thanks very much for the clarification.

  Actually I was more interested in yaffsVersion's effect on oob
layout, if any.

  Let's say I have a 512/16 part that was formatted using old yaffs1 and

	.eccpos = {8, 9, 10, 13, 14, 15}

  and then I run the latest yaffs2 that correctly senses a 512/16 part
and selects yaffsVersion=1.  Since my kernel version is
now > KERNEL_VERSION(2,6,18), I can't access this partition since I'm
now selecting MTD_OOB_AUTO.  I think the OpenWRT folks may have
stumbled upon this issue (see https://dev.openwrt.org/ticket/1779).

  Rick Bronson  

> The yaffsVersion variable, displayed as isYaffs2 in /proc/yaffs, 
> shows which yaffs methods are being used. So called Yaffs1 
> methods are used when the underlying device is a small-page 
> (512) NAND chip. Yaffs2 methods are used when the underlying 
> device is large-page (2k).  Yaffs operates differently on these 
> two types of NAND.
> 
> The "yaffs2" codebase at cvs.aleph1.co.uk:/home/aleph1/cvs 
> supports both page sizes, both sets of methods.  When it runs 
> with a small-page device, it runs much like the original "yaffs" 
> codebase.