X-Git-Url: http://www.aleph1.co.uk/gitweb/?a=blobdiff_plain;ds=sidebyside;f=Documentation%2Fyaffs_on_mtd.html;h=bba25e739469b643ea5c4b24b23b25339a094a8e;hb=11b48ba07062b2975286d468b9a75f7d06293d78;hp=b994fba698f79ed4d1dac972fdb6a5ad51826621;hpb=47e27ba76801d146d5b2ae8edc88a98aab8cc1e8;p=yaffs%2F.git diff --git a/Documentation/yaffs_on_mtd.html b/Documentation/yaffs_on_mtd.html index b994fba..bba25e7 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.

    -

  1. 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.

    +

  2. 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. +

  3. 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

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

  2. 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,18 @@ 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. +

    +



    +