OpenWrt – Blame information for rev 2
?pathlinks?
Rev | Author | Line No. | Line |
---|---|---|---|
1 | office | 1 | --- a/drivers/mtd/Kconfig |
2 | +++ b/drivers/mtd/Kconfig |
||
3 | @@ -184,6 +184,22 @@ config MTD_BCM47XX_PARTS |
||
4 | This provides partitions parser for devices based on BCM47xx |
||
5 | boards. |
||
6 | |||
7 | +config MTD_MYLOADER_PARTS |
||
8 | + tristate "MyLoader partition parsing" |
||
9 | + depends on ADM5120 || ATH25 || ATH79 |
||
10 | + ---help--- |
||
11 | + MyLoader is a bootloader which allows the user to define partitions |
||
12 | + in flash devices, by putting a table in the second erase block |
||
13 | + on the device, similar to a partition table. This table gives the |
||
14 | + offsets and lengths of the user defined partitions. |
||
15 | + |
||
16 | + If you need code which can detect and parse these tables, and |
||
17 | + register MTD 'partitions' corresponding to each image detected, |
||
18 | + enable this option. |
||
19 | + |
||
20 | + You will still need the parsing functions to be called by the driver |
||
21 | + for your particular device. It won't happen automatically. |
||
22 | + |
||
23 | comment "User Modules And Translation Layers" |
||
24 | |||
25 | # |
||
26 | --- a/drivers/mtd/Makefile |
||
27 | +++ b/drivers/mtd/Makefile |
||
28 | @@ -15,6 +15,7 @@ obj-$(CONFIG_MTD_AFS_PARTS) += afs.o |
||
29 | obj-$(CONFIG_MTD_AR7_PARTS) += ar7part.o |
||
30 | obj-$(CONFIG_MTD_BCM63XX_PARTS) += bcm63xxpart.o |
||
31 | obj-$(CONFIG_MTD_BCM47XX_PARTS) += bcm47xxpart.o |
||
32 | +obj-$(CONFIG_MTD_MYLOADER_PARTS) += myloader.o |
||
33 | |||
34 | # 'Users' - code which presents functionality to userspace. |
||
35 | obj-$(CONFIG_MTD_BLKDEVS) += mtd_blkdevs.o |