1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "TI AR7 partitioning parser"
5 TI AR7 partitioning parser support
7 config MTD_BCM47XX_PARTS
8 tristate "BCM47XX partitioning parser"
9 depends on BCM47XX || ARCH_BCM_5301X
11 This provides partitions parser for devices based on BCM47xx
14 config MTD_PARSER_IMAGETAG
15 tristate "Parser for BCM963XX Image Tag format partitions"
16 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
19 Image Tag is the firmware header used by broadcom on their xDSL line
20 of devices. It is used to describe the offsets and lengths of kernel
21 and rootfs partitions.
22 This driver adds support for parsing a partition with an Image Tag
23 header and creates up to two partitions, kernel and rootfs.
26 tristate "ARM Firmware Suite partition parsing"
27 depends on (ARM || ARM64)
29 The ARM Firmware Suite allows the user to divide flash devices into
30 multiple 'images'. Each such image has a header containing its name
33 If you need code which can detect and parse these tables, and
34 register MTD 'partitions' corresponding to each image detected,
37 You will still need the parsing functions to be called by the driver
38 for your particular device. It won't happen automatically. The
39 'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
42 tristate "Parser for TRX format partitions"
43 depends on MTD && (BCM47XX || ARCH_BCM_5301X || COMPILE_TEST)
45 TRX is a firmware format used by Broadcom on their devices. It
46 may contain up to 3/4 partitions (depending on the version).
47 This driver will parse TRX header and report at least two partitions:
50 config MTD_SHARPSL_PARTS
51 tristate "Sharp SL Series NAND flash partition parser"
52 depends on MTD_NAND_SHARPSL || MTD_NAND_TMIO || COMPILE_TEST
54 This provides the read-only FTL logic necessary to read the partition
55 table from the NAND flash of Sharp SL Series (Zaurus) and the MTD
56 partition parser using this code.
58 config MTD_REDBOOT_PARTS
59 tristate "RedBoot partition table parsing"
61 RedBoot is a ROM monitor and bootloader which deals with multiple
62 'images' in flash devices by putting a table one of the erase
63 blocks on the device, similar to a partition table, which gives
64 the offsets, lengths and names of all the images stored in the
67 If you need code which can detect and parse this table, and register
68 MTD 'partitions' corresponding to each image in the table, enable
71 You will still need the parsing functions to be called by the driver
72 for your particular device. It won't happen automatically. The
73 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
78 config MTD_REDBOOT_DIRECTORY_BLOCK
79 int "Location of RedBoot partition table"
82 This option is the Linux counterpart to the
83 CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
86 The option specifies which Flash sectors holds the RedBoot
87 partition table. A zero or positive value gives an absolute
88 erase block number. A negative value specifies a number of
89 sectors before the end of the device.
91 For example "2" means block number 2, "-1" means the last
92 block and "-2" means the penultimate block.
94 config MTD_REDBOOT_PARTS_UNALLOCATED
95 bool "Include unallocated flash regions"
97 If you need to register each unallocated flash region as a MTD
98 'partition', enable this option.
100 config MTD_REDBOOT_PARTS_READONLY
101 bool "Force read-only for RedBoot system images"
103 If you need to force read-only for 'RedBoot', 'RedBoot Config' and
104 'FIS directory' images, enable this option.
106 endif # MTD_REDBOOT_PARTS