target/linux/at91/patches-2.6.22/007-mtd-partition.patch

   1 Index: linux-2.6.22.19/drivers/mtd/devices/at91_dataflash.c
   2 ===================================================================
   3 --- linux-2.6.22.19.orig/drivers/mtd/devices/at91_dataflash.c
   4 +++ linux-2.6.22.19/drivers/mtd/devices/at91_dataflash.c
   5 @@ -173,7 +173,7 @@ static struct mtd_partition static_parti
   6  };
   7  #endif
   8
   9 -static const char *part_probes[] = { "cmdlinepart", NULL, };
  10 +static const char *part_probes[] = { "cmdlinepart", "at91part", NULL, };
  11
  12  #endif
  13
  14 Index: linux-2.6.22.19/drivers/mtd/Kconfig
  15 ===================================================================
  16 --- linux-2.6.22.19.orig/drivers/mtd/Kconfig
  17 +++ linux-2.6.22.19/drivers/mtd/Kconfig
  18 @@ -160,6 +160,12 @@ config MTD_AFS_PARTS
  19           for your particular device. It won't happen automatically. The
  20           'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
  21
  22 +config MTD_AT91_PARTS
  23 +       tristate "Atmel AT91 partitioning support"
  24 +       depends on MTD_PARTITIONS && ARCH_AT91RM9200 && AT91_SPI
  25 +       ---help---
  26 +         Atmel AT91 partitioning support
  27 +
  28  comment "User Modules And Translation Layers"
  29
  30  config MTD_CHAR
  31 Index: linux-2.6.22.19/drivers/mtd/Makefile
  32 ===================================================================
  33 --- linux-2.6.22.19.orig/drivers/mtd/Makefile
  34 +++ linux-2.6.22.19/drivers/mtd/Makefile
  35 @@ -11,6 +11,7 @@ obj-$(CONFIG_MTD_CONCAT)      += mtdconcat.o
  36  obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
  37  obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o
  38  obj-$(CONFIG_MTD_AFS_PARTS)    += afs.o
  39 +obj-$(CONFIG_MTD_AT91_PARTS)   += at91part.o
  40
  41  # 'Users' - code which presents functionality to userspace.
  42  obj-$(CONFIG_MTD_CHAR)         += mtdchar.o