2008-06-06 08:54:13 +00:00
|
|
|
--- a/drivers/mtd/Kconfig
|
|
|
|
|
+++ b/drivers/mtd/Kconfig
|
|
|
|
|
@@ -160,6 +160,22 @@
|
2008-01-30 15:25:48 +00:00
|
|
|
for your particular device. It won't happen automatically. The
|
|
|
|
|
'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
|
|
|
|
|
|
|
|
|
|
+config MTD_MYLOADER_PARTS
|
|
|
|
|
+ tristate "MyLoader partition parsing"
|
|
|
|
|
+ depends on MIPS_ADM5120 && MTD_PARTITIONS
|
|
|
|
|
+ ---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
|
2008-06-06 08:54:13 +00:00
|
|
|
--- a/drivers/mtd/Makefile
|
|
|
|
|
+++ b/drivers/mtd/Makefile
|
|
|
|
|
@@ -11,6 +11,7 @@
|
2008-01-30 15:25:48 +00:00
|
|
|
obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
|
|
|
|
|
obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o
|
|
|
|
|
obj-$(CONFIG_MTD_AFS_PARTS) += afs.o
|
|
|
|
|
+obj-$(CONFIG_MTD_MYLOADER_PARTS) += myloader.o
|
|
|
|
|
|
|
|
|
|
# 'Users' - code which presents functionality to userspace.
|
|
|
|
|
obj-$(CONFIG_MTD_CHAR) += mtdchar.o
|
