Hi, again,

I'm committing the wonderful sin of replying to my own message!  But
thinking about this from a newbie's point of view, it occured to me
that my fundamental disconnect was in not recognizing that "Steven
Hill's nand_ecc.c" *IS* the "ECC functions of the generic MTD-NAND
driver", as referred to in the original help docs for these two
options.

To try and connect the two phrases is probably the biggest motivation
for me in suggesting changes (repeated below) to the Kconfig help
strings.

Again, thanks for listening.

--> Steve Wahl

On Wed, Feb 09, 2005 at 10:57:38AM -0600, Steve Wahl wrote:
> 
> ----------------------Cut here--------------------------------------
>  +config YAFFS_USE_NANDECC
>  +	bool "Use ECC functions of the generic MTD-NAND driver"
>  +	depends on YAFFS_FS
>  +	default y
>  +	help
>  +	  This enables the ECC functions of the generic MTD-NAND driver.
>  +	  This will not work if you are using the old mtd.
>  +
>  +	  NB Use NAND ECC does not work at present with yaffsram.
> ++
> ++	  NB Use NAND ECC has a different ECC byte order than the
> ++	  normal yaffs_ecc.c, and the resulting filesystem format is
> ++	  binary incompatible with a previously existing yaffs filesystem.
> ++	  (This different ordering is the same as yaffs_ecc.c generates
> ++	  when ECC_WRONG_ORDER is turned on.)
>  +
>  +	  If unsure, say Y.
>  +
>  +config YAFFS_ECC_WRONG_ORDER
>  +	bool "Use the same ecc byte order as Steven Hill's nand_ecc.c"
>  +	depends on YAFFS_FS
>  +	help
>  +	  This makes yaffs_ecc.c use the same ecc byte order as
> -+	  Steven Hill's nand_ecc.c. If not set, then you get the
> -+	  same ecc byte order as SmartMedia.
> ++	  Steven Hill's nand_ecc.c (part of the MTD-NAND driver).
> ++	  If not set, then you get the same ecc byte order as SmartMedia.
>  +
>  +	  If unsure, say N.
>  +
> ----------------------Cut here--------------------------------------