diff options
| author | Florian Fainelli <florian@openwrt.org> | 2013-03-14 14:45:56 +0000 |
|---|---|---|
| committer | Florian Fainelli <florian@openwrt.org> | 2013-03-14 14:45:56 +0000 |
| commit | b2e63b8ea81fae72aef69649631cf491bac5306f (patch) | |
| tree | 9a4bc7d83c339b4b842999287e3ae5e5d5d6734a /target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch | |
| parent | 32f3b1e3582701ef6c8c248b9ad0a761c42bbc1b (diff) | |
| download | upstream-b2e63b8ea81fae72aef69649631cf491bac5306f.tar.gz upstream-b2e63b8ea81fae72aef69649631cf491bac5306f.tar.bz2 upstream-b2e63b8ea81fae72aef69649631cf491bac5306f.zip | |
kernel: add support for 3.9-rc2
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 36008
Diffstat (limited to 'target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch')
| -rw-r--r-- | target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch b/target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch new file mode 100644 index 0000000000..0f3379897d --- /dev/null +++ b/target/linux/generic/patches-3.9/430-mtd_myloader_partition_parser.patch @@ -0,0 +1,35 @@ +--- a/drivers/mtd/Kconfig ++++ b/drivers/mtd/Kconfig +@@ -163,6 +163,22 @@ config MTD_BCM47XX_PARTS + This provides partitions parser for devices based on BCM47xx + boards. + ++config MTD_MYLOADER_PARTS ++ tristate "MyLoader partition parsing" ++ depends on ADM5120 || ATHEROS_AR231X || ATHEROS_AR71XX || ATH79 ++ ---help--- ++ MyLoader is a bootloader which allows the user to define partitions ++ in flash devices, by putting a table in the second erase block ++ on the device, similar to a partition table. This table gives the ++ offsets and lengths of the user defined partitions. ++ ++ If you need code which can detect and parse these tables, and ++ register MTD 'partitions' corresponding to each image detected, ++ enable this option. ++ ++ You will still need the parsing functions to be called by the driver ++ for your particular device. It won't happen automatically. ++ + comment "User Modules And Translation Layers" + + config MTD_CHAR +--- a/drivers/mtd/Makefile ++++ b/drivers/mtd/Makefile +@@ -13,6 +13,7 @@ obj-$(CONFIG_MTD_AFS_PARTS) += afs.o + obj-$(CONFIG_MTD_AR7_PARTS) += ar7part.o + obj-$(CONFIG_MTD_BCM63XX_PARTS) += bcm63xxpart.o + obj-$(CONFIG_MTD_BCM47XX_PARTS) += bcm47xxpart.o ++obj-$(CONFIG_MTD_MYLOADER_PARTS) += myloader.o + + # 'Users' - code which presents functionality to userspace. + obj-$(CONFIG_MTD_CHAR) += mtdchar.o |