Lines Matching +full:on +full:- +full:device

2 	tristate "Memory Technology Device (MTD) support"
5 	  used for solid state file systems on embedded devices. This option
8 	  to enumerate the devices which are present and obtain a handle on
16 	depends on m
22 	  WARNING: some of the tests will ERASE entire MTD device which they
30 	  blocks on the device, similar to a partition table, which gives
39 	  for your particular device. It won't happen automatically. The
47 	default "-1"
56 	  sectors before the end of the device.
58 	  For example "2" means block number 2, "-1" means the last
59 	  block and "-2" means the penultimate block.
68 	bool "Force read-only for RedBoot system images"
70 	  If you need to force read-only for 'RedBoot', 'RedBoot Config' and
77 	depends on MTD
84 	  for your particular device. It won't happen automatically. The
91 	  <mtddef>  := <mtd-id>:<partdef>[,<partdef>]
93 	  <mtd-id>  := unique id used in mapping driver/device
94 	  <size>    := standard linux memsize OR "-" to denote all
104 	  1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
105 	  mtdparts=sa1100:-
107 	  Same flash, but 2 named partitions, the first one being read-only:
108 	  mtdparts=sa1100:256k(ARMboot)ro,-(root)
114 	depends on (ARM || ARM64)
125 	  for your particular device. It won't happen automatically. The
131 	depends on OF
144 	depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
152 	depends on BCM47XX || ARCH_BCM_5301X
154 	  This provides partitions parser for devices based on BCM47xx
164 # MTD block device support is select'ed if needed
170 	tristate "Caching block device access to MTD devices"
171 	depends on BLOCK
176 	  on RAM chips in this manner. This block device is a user of MTD
180 	  System(s) to obtain a handle on the MTD device when it's mounted
182 	  of the mtdblock device).
185 	  on flash chips to emulate a smaller block size. Needless to say,
193 	tristate "Readonly block device access to MTD devices"
194 	depends on MTD_BLOCK!=y && BLOCK
197 	  This allows you to mount read-only file systems (such as cramfs)
198 	  from an MTD device, without the overhead (and danger) of the caching
206 	depends on BLOCK
210 	  is part of the PCMCIA specification. It uses a kind of pseudo-
211 	  file system on a flash device to emulate a block device with
212 	  512-byte sectors, on top of which you put a 'normal' file system.
216 	  legal - in the USA you are only permitted to use this on PCMCIA
223 	depends on BLOCK
227 	  used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
228 	  file system on a flash device to emulate a block device with
229 	  512-byte sectors, on top of which you put a 'normal' file system.
233 	  legal - in the USA you are only permitted to use this on DiskOnChip
240 	depends on NFTL
243 	  on the DiskOnChip.
247 	depends on BLOCK
251 	  Layer which is used on M-Systems' newer DiskOnChip devices. It
252 	  uses a kind of pseudo-file system on a flash device to emulate
253 	  a block device with 512-byte sectors, on top of which you put
258 	  legal - in the USA you are only permitted to use this on DiskOnChip
265 	depends on BLOCK
276 	depends on BLOCK
285 	depends on BLOCK
306 	tristate "Swap on MTD device support"
307 	depends on MTD && SWAP
310 	  Provides volatile block device driver on top of mtd partition
316 	bool "Retain master device when partitioned"
318 	depends on MTD
324 	  leaves the master in even if the device is partitioned. It also makes
325 	  the parent of the partition device be the master device, rather than
338 source "drivers/mtd/spi-nor/Kconfig"