X-Git-Url: http://www.aleph1.co.uk/gitweb/?a=blobdiff_plain;f=Documentation%2Fyaffs_on_mtd.html;h=f35591eb58af416e0d3407beb89b4b8c3fa00188;hb=3b2905b66368db2b05df750b5abf4b41c6efcfbd;hp=b994fba698f79ed4d1dac972fdb6a5ad51826621;hpb=cd0bc12e8f2c6cdec550b03a324a5917e6441f1b;p=yaffs%2F.git diff --git a/Documentation/yaffs_on_mtd.html b/Documentation/yaffs_on_mtd.html index b994fba..f35591e 100644 --- a/Documentation/yaffs_on_mtd.html +++ b/Documentation/yaffs_on_mtd.html @@ -6,11 +6,11 @@ - +

Running up YAFFS using the MTD interface

Here are the steps required to get YAFFS going with the +

Here are the steps required to get YAFFS going with the NANDemulation MTD that I have written.

Warning: This is experimental stuff that plugs into the kernel. It has only @@ -21,10 +21,10 @@ you're working from the 2.4.18 kernel code base.

Preparing the kernel

First off, you need to patch the mtdcore services.

-
Replace the devices/mtd/mtdpart.c file with the one enclosed. - This patches the problem where special NAND functions are not being - copied through the partition handler. The changes are marked with a - comment containing my initials cdhm.
+
Replace the mtd files with the latest from the mtd cvs. This + fixes problems where special NAND functions are not being copied + through the partition handler. +

Build the kernel including the following configurations to support mtd.

@@ -39,14 +39,13 @@ used only to find the device for mounting

CONFIG_MTD_DEBUG=y

CONFIG_MTD_DEBUG_VERBOSE=3
-

Setting up yaffs

Run the mtd utility MAKEDEV to make the /dev/mtdxxx entries.

Load up the NANDemul MTD by typing
#/sbin/insmod mtdemul/nandemul.o
You should now be able to see the - device in the mtd list by typing
#cat + device in the mtd list by typing
#cat /proc/mtd
If all is well, the device will now be accessible as /dev/mtd0 and /dev/mtdblock0 (or whatever).
@@ -69,8 +68,23 @@ real NAND device.
NANDemul tests out the mtd interface so in theory it should work on real NAND too.

Note though that since YAFFS applies the -ECC, it does not expect the NAND device to be applying ECC. You -probably want to configure the NAND driver with ECC disabled.
+ECC and verify, it does not expect the NAND device to be applying ECC +or verification. +
+
You probably need to configure the NAND +with the following disabled:
+
CONFIG_MTD_NAND_ECC
+
CONFIG_MTD_NAND_VERIFY_WRITE
+
Nick Banes has had YAFFS working on real +NAND, with a few issues. +
+

+
+
$Id: yaffs_on_mtd.html,v 1.3 2002-11-26 01:15:38 charles Exp $
+

+
+

+