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