mirror of
https://github.com/torvalds/linux.git
synced 2024-11-22 20:22:09 +00:00
mtd: afs: Move AFS partition parser to parsers subdir
This moves the AFS (ARM Firmware Suite) partition parser for NOR flash down into the parsers subdirectory. Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Richard Weinberger <richard@nod.at>
This commit is contained in:
parent
251f26c9e8
commit
2aa3b8e1de
@ -60,22 +60,6 @@ config MTD_CMDLINE_PARTS
|
|||||||
|
|
||||||
If unsure, say 'N'.
|
If unsure, say 'N'.
|
||||||
|
|
||||||
config MTD_AFS_PARTS
|
|
||||||
tristate "ARM Firmware Suite partition parsing"
|
|
||||||
depends on (ARM || ARM64)
|
|
||||||
help
|
|
||||||
The ARM Firmware Suite allows the user to divide flash devices into
|
|
||||||
multiple 'images'. Each such image has a header containing its name
|
|
||||||
and offset/size etc.
|
|
||||||
|
|
||||||
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. The
|
|
||||||
'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
|
|
||||||
|
|
||||||
config MTD_OF_PARTS
|
config MTD_OF_PARTS
|
||||||
tristate "OpenFirmware partitioning information support"
|
tristate "OpenFirmware partitioning information support"
|
||||||
default y
|
default y
|
||||||
|
@ -9,7 +9,6 @@ mtd-y := mtdcore.o mtdsuper.o mtdconcat.o mtdpart.o mtdchar.o
|
|||||||
|
|
||||||
obj-$(CONFIG_MTD_OF_PARTS) += ofpart.o
|
obj-$(CONFIG_MTD_OF_PARTS) += ofpart.o
|
||||||
obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o
|
obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o
|
||||||
obj-$(CONFIG_MTD_AFS_PARTS) += afs.o
|
|
||||||
obj-$(CONFIG_MTD_AR7_PARTS) += ar7part.o
|
obj-$(CONFIG_MTD_AR7_PARTS) += ar7part.o
|
||||||
obj-$(CONFIG_MTD_BCM63XX_PARTS) += bcm63xxpart.o
|
obj-$(CONFIG_MTD_BCM63XX_PARTS) += bcm63xxpart.o
|
||||||
obj-$(CONFIG_MTD_BCM47XX_PARTS) += bcm47xxpart.o
|
obj-$(CONFIG_MTD_BCM47XX_PARTS) += bcm47xxpart.o
|
||||||
|
@ -9,6 +9,22 @@ config MTD_PARSER_IMAGETAG
|
|||||||
This driver adds support for parsing a partition with an Image Tag
|
This driver adds support for parsing a partition with an Image Tag
|
||||||
header and creates up to two partitions, kernel and rootfs.
|
header and creates up to two partitions, kernel and rootfs.
|
||||||
|
|
||||||
|
config MTD_AFS_PARTS
|
||||||
|
tristate "ARM Firmware Suite partition parsing"
|
||||||
|
depends on (ARM || ARM64)
|
||||||
|
help
|
||||||
|
The ARM Firmware Suite allows the user to divide flash devices into
|
||||||
|
multiple 'images'. Each such image has a header containing its name
|
||||||
|
and offset/size etc.
|
||||||
|
|
||||||
|
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. The
|
||||||
|
'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
|
||||||
|
|
||||||
config MTD_PARSER_TRX
|
config MTD_PARSER_TRX
|
||||||
tristate "Parser for TRX format partitions"
|
tristate "Parser for TRX format partitions"
|
||||||
depends on MTD && (BCM47XX || ARCH_BCM_5301X || COMPILE_TEST)
|
depends on MTD && (BCM47XX || ARCH_BCM_5301X || COMPILE_TEST)
|
||||||
|
@ -1,4 +1,5 @@
|
|||||||
obj-$(CONFIG_MTD_PARSER_IMAGETAG) += parser_imagetag.o
|
obj-$(CONFIG_MTD_PARSER_IMAGETAG) += parser_imagetag.o
|
||||||
|
obj-$(CONFIG_MTD_AFS_PARTS) += afs.o
|
||||||
obj-$(CONFIG_MTD_PARSER_TRX) += parser_trx.o
|
obj-$(CONFIG_MTD_PARSER_TRX) += parser_trx.o
|
||||||
obj-$(CONFIG_MTD_SHARPSL_PARTS) += sharpslpart.o
|
obj-$(CONFIG_MTD_SHARPSL_PARTS) += sharpslpart.o
|
||||||
obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
|
obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
|
||||||
|
Loading…
Reference in New Issue
Block a user